<?xml version='1.0' encoding='utf-8'?>
<TriX xmlns:brick="https://brickschema.org/schema/Brick#" xmlns:csvw="http://www.w3.org/ns/csvw#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcat="http://www.w3.org/ns/dcat#" xmlns:dcmitype="http://purl.org/dc/dcmitype/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:dcam="http://purl.org/dc/dcam/" xmlns:doap="http://usefulinc.com/ns/doap#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:geo="http://www.opengis.net/ont/geosparql#" xmlns:odrl="http://www.w3.org/ns/odrl/2/" xmlns:org="http://www.w3.org/ns/org#" xmlns:prof="http://www.w3.org/ns/dx/prof/" xmlns:prov="http://www.w3.org/ns/prov#" xmlns:qb="http://purl.org/linked-data/cube#" xmlns:sh="http://www.w3.org/ns/shacl#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:sosa="http://www.w3.org/ns/sosa/" xmlns:ssn="http://www.w3.org/ns/ssn/" xmlns:time="http://www.w3.org/2006/time#" xmlns:vann="http://purl.org/vocab/vann/" xmlns:void="http://rdfs.org/ns/void#" xmlns:wgs="https://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:schema="http://schema.org/" xmlns="http://www.w3.org/2004/03/trix/trix-1/">
  <graph>
    <uri>https://chasemgrimm.com/publications/research#graph</uri>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Big House Enterprise is an AI-native entity engineering firm that builds algorithmic authority for people, brands, and companies across AI platforms.</plainLiteral>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Big House Enterprise</plainLiteral>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://lei.bloomberg.com/leis/view/254900PDJFA7CEG5JE91</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://pressroom.prlog.org/BigHouseEnterprise/</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.bbb.org/us/ia/johnston/profile/artificial-intelligence/big-house-enterprise-llc-0664-32159365</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.crunchbase.com/organization/big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.f6s.com/big-house-enterprise/</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/g/11xztrvrl2</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.linkedin.com/company/big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.wikidata.org/wiki/Q139918459</uri>
    </triple>
    <triple>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://bighouseenterprise.com</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#country-united-states</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>United States</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#country-united-states</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Country</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#credential-bachelor-of-science-in-industrial-engineering</uri>
      <uri>http://schema.org/credentialCategory</uri>
      <plainLiteral>degree</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#credential-bachelor-of-science-in-industrial-engineering</uri>
      <uri>http://schema.org/dateCreated</uri>
      <typedLiteral datatype="http://schema.org/Date">2017</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#credential-bachelor-of-science-in-industrial-engineering</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Bachelor of Science in Industrial Engineering</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#credential-bachelor-of-science-in-industrial-engineering</uri>
      <uri>http://schema.org/recognizedBy</uri>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#credential-bachelor-of-science-in-industrial-engineering</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/EducationalOccupationalCredential</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-algorithmic-trading</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Developing quantitative trading strategies that apply systems engineering principles to financial markets. Focus on systematic approaches that leverage the same foundational methods used in other technical domains.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-algorithmic-trading</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Algorithmic Trading</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-algorithmic-trading</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/07h5dh</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-algorithmic-trading</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>intermediate, 4 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-algorithmic-trading</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-human-factors-engineering</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Conducting user research and designing systems that account for operator knowledge, preferences, and cognitive limitations. Experience validating simulator fidelity and developing knowledge assessment instruments for population segmentation.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-human-factors-engineering</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Human Factors Engineering</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-human-factors-engineering</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/02m8q</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-human-factors-engineering</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>intermediate, 3 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-human-factors-engineering</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-machine-learning</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Developing and deploying machine learning models for classification, prediction, and pattern recognition. Applications span scientific trend forecasting, traffic incident prediction, and financial signal extraction.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-machine-learning</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Machine Learning</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-machine-learning</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/01hyh_</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-machine-learning</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>advanced, 7 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-machine-learning</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-natural-language-processing</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Designing and implementing NLP pipelines for extracting structured information from unstructured text. Experience spans scientific literature mining, financial document analysis, and crowdsourced data processing. Core competencies include named entity recognition, relationship extraction, topic modeling, and trend analysis at scale.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-natural-language-processing</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Natural Language Processing</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-natural-language-processing</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/05flf</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-natural-language-processing</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>expert, 7 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-natural-language-processing</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-operations-research</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Applying optimization and statistical methods to improve decision-making in investment and operational contexts. Experience with portfolio optimization, resource allocation, and process improvement across equities, fixed income, and asset management divisions.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-operations-research</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Operations Research</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-operations-research</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/0bx8h</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-operations-research</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>advanced, 6 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-operations-research</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-systems-engineering</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Applying rigorous systems thinking to decompose complex problems across diverse domains. Expertise in requirements analysis, functional decomposition, interface design, and tradeoff analysis. Philosophy centers on the belief that good systems engineering makes any problem approachable.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-systems-engineering</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Systems Engineering</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-systems-engineering</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/06xj3</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-systems-engineering</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>expert, 10 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-systems-engineering</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-text-analytics</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Building text analytics infrastructure for processing unstructured data at scale. Specialization in financial and enterprise domains including regulatory filings, earnings calls, and corporate communications. Experience extracting risk signals and causal relationships from document corpora.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-text-analytics</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Text Analytics</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-text-analytics</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/01v59d</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-text-analytics</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>expert, 8 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-text-analytics</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-virtual-reality-simulation</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Evaluating and validating VR systems for training and research applications. Experience assessing simulator fidelity through structured user studies and developing validation methodologies for mixed-reality interfaces.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-virtual-reality-simulation</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Virtual Reality Simulation</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-virtual-reality-simulation</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/07_ny</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-virtual-reality-simulation</uri>
      <uri>http://schema.org/termCode</uri>
      <plainLiteral>intermediate, 3 years</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#definedterm-virtual-reality-simulation</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/DefinedTerm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university-alumniof</uri>
      <uri>http://schema.org/alumniOf</uri>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university-alumniof</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2017</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university-alumniof</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Bachelor of Science, Industrial Engineering</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university-alumniof</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/OrganizationRole</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Iowa State University</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/03v6t</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://www.iastate.edu/</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/CollegeOrUniversity</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2-thumbnail</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://images.bighouseenterprise.com/chase-grimm/chase-grimm/primary/chase-pfp-d045a2-thumb.webp</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2-thumbnail</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ImageObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/about</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/caption</uri>
      <plainLiteral>Chase Grimm Headshot</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://images.bighouseenterprise.com/chase-grimm/chase-grimm/primary/chase-pfp-d045a2.webp</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/copyrightYear</uri>
      <plainLiteral>2026</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Chase Grimm Headshot</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>image/webp</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/height</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">360</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Chase Grimm Headshot</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/thumbnail</uri>
      <uri>https://chasemgrimm.com/#image-b63e13c2-thumbnail</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://images.bighouseenterprise.com/chase-grimm/chase-grimm/primary/chase-pfp-d045a2.webp</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://schema.org/width</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">360</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ImageObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Engineer at Alliant</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2026-09-07</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Engineer</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Partner at Big House Enterprise</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2025-11-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Pioneering entity engineering to build algorithmic authority for companies, brands, and executives across AI search platforms. We design machine-readable entity infrastructure so systems like ChatGPT, Perplexity, Claude, and Google accurately recognize, cite, and recommend your business.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Partner</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer-role</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2025-10-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Senior Engineer at Consilience AI</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2022-01-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Senior Engineer at Consilience AI, building specialized language models for financial and enterprise domains—extracting risk signals and causal relationships from regulatory filings, earnings calls, and corporate communications.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Senior Engineer</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor-role</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2015-05-31</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Tutor at Iowa State University</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2015-02-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Facilitated group discussions with up to four students. Utilized knowledge of subject matter to tutor and share knowledge with peers.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Tutor</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant-role</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2017-12-31</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Undergraduate Research Assistant at Iowa State University</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2015-04-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Undergraduate Research Assistant in Industrial Engineering at Iowa State University—conducted user studies for agricultural technology, developed Android applications for equipment automation, and built predictive models for irregular traffic using web/social media data and text mining in R.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Undergraduate Research Assistant</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern-role</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2017-08-31</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>UX/UI Software Development Intern at Optum</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2017-06-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>UI/UX Software Development Intern at Optum Health, contributing to a team-based software redesign with emphasis on user research and secure web development in Spring.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>UX/UI Software Development Intern</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist-role</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2022-01-31</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Data &amp; Operations Research Scientist at Principal Financial Group</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2017-12-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Data &amp; Operations Research Scientist applying optimization and statistical methods across Principal's investment divisions to improve portfolio performance and operational efficiency in equities, fixed income, and asset management.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Data &amp; Operations Research Scientist</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8-role</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2017-03-31</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8-role</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8-role</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>Master Scheduling Data Consolidation Analyst, Senior Intern at Rockwell Collins</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8-role</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2016-05-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8-role</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Master Scheduling Data Consolidation Analyst (Senior Intern) at Collins Aerospace—built web-based tools to consolidate disparate datasets and provided analytics aligning cost of sales with production plans across inventory, customer satisfaction, and business KPIs. Tech stack: Excel, VBA, R, Python, SQL, SAP, Access.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Master Scheduling Data Consolidation Analyst, Senior Intern</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Occupation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-consilience-ai</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Consilience AI</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-consilience-ai</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://consilience.ai/</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-consilience-ai</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Organization</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center-affiliation</uri>
      <uri>http://schema.org/affiliation</uri>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center-affiliation</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Micro-g NExT Competition participant. Developed an EVA Surface Sampling Device (SSD) with a team of peer engineering students. Designed and built multiple prototypes using 3D printing. Traveled to NASA Neutral Buoyancy Lab to test the device and gave multiple presentations.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center-affiliation</uri>
      <uri>http://schema.org/endDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2015-08-31</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center-affiliation</uri>
      <uri>http://schema.org/roleName</uri>
      <plainLiteral>collaborator</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center-affiliation</uri>
      <uri>http://schema.org/startDate</uri>
      <typedLiteral datatype="http://schema.org/Date">2015-02-01</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center-affiliation</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/OrganizationRole</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>NASA Johnson Space Center</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.google.com/search?kgmid=/m/0d_q3</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://www.nasa.gov/johnson/</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Organization</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-2017-systems-and-information-engineering-design-sympo-2bacdd</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>2017 Systems and Information Engineering Design Symposium (SIEDS)</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-2017-systems-and-information-engineering-design-sympo-2bacdd</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Periodical</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-computers-and-electronics-in-agriculture</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Computers and Electronics in Agriculture</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-computers-and-electronics-in-agriculture</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Periodical</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-journal-of-proteome-research</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Journal of Proteome Research</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-journal-of-proteome-research</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Periodical</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-proceedings-of-the-human-factors-and-ergonomics-socie-12c8a1</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#periodical-proceedings-of-the-human-factors-and-ergonomics-socie-12c8a1</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Periodical</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-birth-place-address</uri>
      <uri>http://schema.org/addressCountry</uri>
      <plainLiteral>United States</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-birth-place-address</uri>
      <uri>http://schema.org/addressRegion</uri>
      <plainLiteral>Iowa</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-birth-place-address</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/PostalAddress</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-birth-place</uri>
      <uri>http://schema.org/address</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm-birth-place-address</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-birth-place</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Place</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-contact-general</uri>
      <uri>http://schema.org/contactType</uri>
      <plainLiteral>General</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-contact-general</uri>
      <uri>http://schema.org/email</uri>
      <plainLiteral>contact@chasemgrimm.com</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm-contact-general</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ContactPoint</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/additionalName</uri>
      <plainLiteral>Morgan</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/affiliation</uri>
      <uri>https://chasemgrimm.com/#org-nasa-johnson-space-center-affiliation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/alumniOf</uri>
      <uri>https://chasemgrimm.com/#eduorg-iowa-state-university-alumniof</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/award</uri>
      <plainLiteral>Academic All-State Football (Iowa High School Athletic Association)</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/award</uri>
      <plainLiteral>Dean's List (Iowa State University)</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/award</uri>
      <plainLiteral>Governor's Scholar Recipient (State of Iowa)</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/award</uri>
      <plainLiteral>KWWL Best of Class (KWWL)</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/award</uri>
      <plainLiteral>Valedictorian (High School)</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/birthDate</uri>
      <typedLiteral datatype="http://schema.org/Date">1996-05-15</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/birthPlace</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm-birth-place</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/contactPoint</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm-contact-general</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Chase Grimm is a systems engineer working across AI, text analytics, and algorithmic trading, applying rigorous systems thinking to solve complex problems across diverse domains.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/familyName</uri>
      <plainLiteral>Grimm</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/gender</uri>
      <plainLiteral>Male</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/givenName</uri>
      <plainLiteral>Chase</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasCredential</uri>
      <uri>https://chasemgrimm.com/#credential-bachelor-of-science-in-industrial-engineering</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-alliant-engineer-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-big-house-enterprise-partner-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-consilience-ai-senior-engineer-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-tutor-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-iowa-state-university-undergraduate-research-assistant-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-optum-uxui-software-development-intern-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-principal-financial-group-data-operations-research-scientist-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/hasOccupation</uri>
      <uri>https://chasemgrimm.com/#occupation-rockwell-collins-master-scheduling-data-consolidation-9771e8-role</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/honorificSuffix</uri>
      <plainLiteral>CAP, PMP</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/image</uri>
      <uri>https://chasemgrimm.com/#image-b63e13c2</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/jobTitle</uri>
      <plainLiteral>Senior Engineer</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-algorithmic-trading</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-human-factors-engineering</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-machine-learning</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-natural-language-processing</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-operations-research</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-systems-engineering</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-text-analytics</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsAbout</uri>
      <uri>https://chasemgrimm.com/#definedterm-virtual-reality-simulation</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsLanguage</uri>
      <plainLiteral>Chinese</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/knowsLanguage</uri>
      <plainLiteral>English</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Chase Grimm</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/nationality</uri>
      <uri>https://chasemgrimm.com/#country-united-states</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://isni.org/isni/0000000530566213</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://muckrack.com/chasegrimm/bio</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://orcid.org/0009-0001-7969-3190</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://scholar.google.com/citations?user=D_piH2sAAAAJ&amp;hl=en</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://www.linkedin.com/in/chasemgrimm/</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://x.com/chasemgrimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://chasemgrimm.com</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://schema.org/worksFor</uri>
      <uri>https://chasemgrimm.com/#org-consilience-ai</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/Person</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/abstract</uri>
      <plainLiteral>Gaining insight into the unique characteristics of participants during user research is a valuable tool for both recruitment and understanding differences within the target population. This work describes an agricultural harvest knowledge survey that was created for user research studies that observed experienced combine operators driving a combine simulator in virtual crop fields. Two variations of the survey were designed, utilized, and evaluated in two separate studies. Both studies found a difference between low and high knowledge operators' performance on the knowledge survey in addition to performance differences. Based on the success of this survey as a population segmentation tool, the authors recommend three criteria for the design of future knowledge surveys in other domains: 1) use real world scenarios, 2) ensure question are neither too difficult nor too easy, and 3) ask the minimum number of questions to identify operator knowledge successfully. Future research aims to create a tool that can discern between system experts (with deep understanding of the system) and practice experts (who primarily have the wisdom of experience).</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/author</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/datePublished</uri>
      <typedLiteral datatype="http://schema.org/Date">2016-09-08T00:00:00+00:00</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Gaining insight into the unique characteristics of participants during user research is a valuable tool for both recruitment and understanding differences within the target population. This work describes an agricultural harvest knowledge survey that was created for user research studies that observed experienced combine operators driving a combine simulator in virtual crop fields. Two variations of the survey were designed, utilized, and evaluated in two separate studies. Both studies found a difference between low and high knowledge operators' performance on the knowledge survey in addition to performance differences. Based on the success of this survey as a population segmentation tool, the authors recommend three criteria for the design of future knowledge surveys in other domains: 1) use real world scenarios, 2) ensure question are neither too difficult nor too easy, and 3) ask the minimum number of questions to identify operator knowledge successfully. Future research aims to create a tool that can discern between system experts (with deep understanding of the system) and practice experts (who primarily have the wisdom of experience).</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/headline</uri>
      <plainLiteral>An Agricultural Harvest Knowledge Survey to Distinguish Types of Expertise</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/isPartOf</uri>
      <uri>https://chasemgrimm.com/#periodical-proceedings-of-the-human-factors-and-ergonomics-socie-12c8a1</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>An Agricultural Harvest Knowledge Survey to Distinguish Types of Expertise</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://doi.org/10.1177/1541931213601465</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://journals.sagepub.com/doi/10.1177/1541931213601465</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ScholarlyArticle</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/abstract</uri>
      <plainLiteral>Large social events can influence traffic conditions and possibly lead to jams and incidents. This study leverages crowdsourced data to analytically evaluate the relationship between social events and traffic incidents in the city of Chicago. In particular, we collected data on social events from scraping online webpages, as well as traffic data from a twitter account that posted irregular traffic incidents based on a crowdsourced navigation application (Waze). Using these two sources the relationship between social events and the occurrence of traffic incidents was investigated. The total number social events and their categories for each region and its neighboring regions were used to build models that predicted the chance of a traffic incident occurrence. Based on the analysis, we demonstrated the variables that indicated significant influence on the chance of a traffic incident occurrence in the same day, such as the number of festivals and fairs, total number of events in the (neighboring) region. We have also developed and tested several models to predict the traffic incidents. The results indicated that using solely online listed social events may not be sufficient for traffic prediction. Although the accuracies are not considerable for an independent model, it clearly indicates that the additional information provided by social events will be a valuable addition to the existing traffic prediction models.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/author</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/datePublished</uri>
      <typedLiteral datatype="http://schema.org/Date">2017-04-01T00:00:00+00:00</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Large social events can influence traffic conditions and possibly lead to jams and incidents. This study leverages crowdsourced data to analytically evaluate the relationship between social events and traffic incidents in the city of Chicago. In particular, we collected data on social events from scraping online webpages, as well as traffic data from a twitter account that posted irregular traffic incidents based on a crowdsourced navigation application (Waze). Using these two sources the relationship between social events and the occurrence of traffic incidents was investigated. The total number social events and their categories for each region and its neighboring regions were used to build models that predicted the chance of a traffic incident occurrence. Based on the analysis, we demonstrated the variables that indicated significant influence on the chance of a traffic incident occurrence in the same day, such as the number of festivals and fairs, total number of events in the (neighboring) region. We have also developed and tested several models to predict the traffic incidents. The results indicated that using solely online listed social events may not be sufficient for traffic prediction. Although the accuracies are not considerable for an independent model, it clearly indicates that the additional information provided by social events will be a valuable addition to the existing traffic prediction models.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/headline</uri>
      <plainLiteral>Investigating the relationship between traffic incidents and public events: A case study</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/isPartOf</uri>
      <uri>https://chasemgrimm.com/#periodical-2017-systems-and-information-engineering-design-sympo-2bacdd</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Investigating the relationship between traffic incidents and public events: A case study</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://doi.org/10.1109/sieds.2017.7937715</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://ieeexplore.ieee.org/document/7937715</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-24797b</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ScholarlyArticle</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/abstract</uri>
      <plainLiteral>The trends of the last 20 years in biotechnology were revealed using artificial intelligence and natural language processing (NLP) of publicly available data. Implementing this 'science-of-science' approach, we capture convergent trends in the field of proteomics in both technology development and application across the phylogenetic tree of life. With major gaps in our knowledge about protein composition, structure, and location over time, we report trends in persistent, popular approaches and emerging technologies across 94 ideas from a corpus of 29 journals in PubMed over two decades. New metrics for clusters of these ideas reveal the progression and popularity of emerging approaches like single-cell, spatial, compositional, and chemical proteomics designed to better capture protein-level chemistry and biology. This analysis of the proteomics literature with advanced analytic tools quantifies the Rate of Rise for a next generation of technologies to better define, quantify, and visualize the multiple dimensions of the proteome that will transform our ability to measure and understand proteins in the coming decade.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/author</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/datePublished</uri>
      <typedLiteral datatype="http://schema.org/Date">2024-02-02T00:00:00+00:00</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>The trends of the last 20 years in biotechnology were revealed using artificial intelligence and natural language processing (NLP) of publicly available data. Implementing this 'science-of-science' approach, we capture convergent trends in the field of proteomics in both technology development and application across the phylogenetic tree of life. With major gaps in our knowledge about protein composition, structure, and location over time, we report trends in persistent, popular approaches and emerging technologies across 94 ideas from a corpus of 29 journals in PubMed over two decades. New metrics for clusters of these ideas reveal the progression and popularity of emerging approaches like single-cell, spatial, compositional, and chemical proteomics designed to better capture protein-level chemistry and biology. This analysis of the proteomics literature with advanced analytic tools quantifies the Rate of Rise for a next generation of technologies to better define, quantify, and visualize the multiple dimensions of the proteome that will transform our ability to measure and understand proteins in the coming decade.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/headline</uri>
      <plainLiteral>Parsing 20 Years of Public Data by AI Maps Trends in Proteomics and Forecasts Technology</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/isPartOf</uri>
      <uri>https://chasemgrimm.com/#periodical-journal-of-proteome-research</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Parsing 20 Years of Public Data by AI Maps Trends in Proteomics and Forecasts Technology</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://doi.org/10.1021/acs.jproteome.3c00430</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://pubs.acs.org/doi/10.1021/acs.jproteome.3c00430</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ScholarlyArticle</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/abstract</uri>
      <plainLiteral>Research, development, testing, and operator training of large agricultural harvesting equipment has become increasingly expensive and complex. Operational simulators can offset these costs, but it is critical to evaluate the fidelity of the simulator experience to ensure that it will lead to operator behaviors that match those in the real world. This research describes a validation process for new visual cues within simulators and focuses on the presentation and fidelity of cues in a combine harvest simulator. The fully functional immersive combine simulator in this work provides a mixed-reality interface that combines a physically accurate operator interface with displays of virtual reality (VR) combine header and grain. Grain combine operators participated to assess how well they perceived the VR cues as representing actual field and crop activity. Results showed that operators successfully identified 85% of the visual cues in the combine simulator and recognized when these cues indicated machine settings adjustment needs but that operators' ability to choose the correct action to take correlated with their knowledge of the combine. Results also showed wide variation in the number of the grain combine's head reel adjustments made by operators, likely reflecting strong individual preferences or habits around reel adjustment. Operators' number of adjustment interactions with the reel was also significantly correlated with the number of correct actions chosen, suggesting that careful attention to the reel is related to good farming performance. This research demonstrates the importance of taking operator knowledge and preferences into account when designing new agricultural products and offers a systematic method of validating cues within an agricultural simulator.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/author</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/datePublished</uri>
      <typedLiteral datatype="http://schema.org/Date">2019-05-01T00:00:00+00:00</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Research, development, testing, and operator training of large agricultural harvesting equipment has become increasingly expensive and complex. Operational simulators can offset these costs, but it is critical to evaluate the fidelity of the simulator experience to ensure that it will lead to operator behaviors that match those in the real world. This research describes a validation process for new visual cues within simulators and focuses on the presentation and fidelity of cues in a combine harvest simulator. The fully functional immersive combine simulator in this work provides a mixed-reality interface that combines a physically accurate operator interface with displays of virtual reality (VR) combine header and grain. Grain combine operators participated to assess how well they perceived the VR cues as representing actual field and crop activity. Results showed that operators successfully identified 85% of the visual cues in the combine simulator and recognized when these cues indicated machine settings adjustment needs but that operators' ability to choose the correct action to take correlated with their knowledge of the combine. Results also showed wide variation in the number of the grain combine's head reel adjustments made by operators, likely reflecting strong individual preferences or habits around reel adjustment. Operators' number of adjustment interactions with the reel was also significantly correlated with the number of correct actions chosen, suggesting that careful attention to the reel is related to good farming performance. This research demonstrates the importance of taking operator knowledge and preferences into account when designing new agricultural products and offers a systematic method of validating cues within an agricultural simulator.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/headline</uri>
      <plainLiteral>The importance of operator knowledge in evaluating virtual reality cue fidelity</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/isPartOf</uri>
      <uri>https://chasemgrimm.com/#periodical-computers-and-electronics-in-agriculture</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>The importance of operator knowledge in evaluating virtual reality cue fidelity</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/sameAs</uri>
      <uri>https://doi.org/10.1016/j.compag.2019.03.026</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://www.sciencedirect.com/science/article/abs/pii/S0168169918309657?via%3Dihub</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ScholarlyArticle</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#website</uri>
      <uri>http://schema.org/description</uri>
      <plainLiteral>Chase Grimm is an AI systems engineer transforming complex challenges into robust AI systems through rigorous engineering and pragmatic design.</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#website</uri>
      <uri>http://schema.org/inLanguage</uri>
      <plainLiteral>en</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#website</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Chase Grimm's Personal Website</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#website</uri>
      <uri>http://schema.org/publisher</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#website</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://chasemgrimm.com</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/#website</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/WebSite</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-1</uri>
      <uri>http://schema.org/item</uri>
      <plainLiteral>https://chasemgrimm.com</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-1</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Home</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-1</uri>
      <uri>http://schema.org/position</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">1</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-1</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ListItem</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-2</uri>
      <uri>http://schema.org/item</uri>
      <plainLiteral>https://chasemgrimm.com/publications</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-2</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Publications</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-2</uri>
      <uri>http://schema.org/position</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">2</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-2</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ListItem</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-3</uri>
      <uri>http://schema.org/item</uri>
      <plainLiteral>https://chasemgrimm.com/publications/research</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-3</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Research</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-3</uri>
      <uri>http://schema.org/position</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">3</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-3</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ListItem</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb</uri>
      <uri>http://schema.org/itemListElement</uri>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-1</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb</uri>
      <uri>http://schema.org/itemListElement</uri>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-2</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb</uri>
      <uri>http://schema.org/itemListElement</uri>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb-item-3</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/BreadcrumbList</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-1</uri>
      <uri>http://schema.org/item</uri>
      <uri>https://chasemgrimm.com/#scholarly-parsing-20-years-of-public-data-by-ai-maps-trends-in-6d5020</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-1</uri>
      <uri>http://schema.org/position</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">1</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-1</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ListItem</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-2</uri>
      <uri>http://schema.org/item</uri>
      <uri>https://chasemgrimm.com/#scholarly-the-importance-of-operator-knowledge-in-evaluating-vi-5a28c0</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-2</uri>
      <uri>http://schema.org/position</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">2</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-2</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ListItem</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-3</uri>
      <uri>http://schema.org/item</uri>
      <uri>https://chasemgrimm.com/#scholarly-investigating-the-relationship-between-traffic-incide-a119f0</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-3</uri>
      <uri>http://schema.org/position</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">3</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-3</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ListItem</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-4</uri>
      <uri>http://schema.org/item</uri>
      <uri>https://chasemgrimm.com/#scholarly-an-agricultural-harvest-knowledge-survey-to-distingui-56b11e</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-4</uri>
      <uri>http://schema.org/position</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">4</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-4</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ListItem</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
      <uri>http://schema.org/itemListElement</uri>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-1</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
      <uri>http://schema.org/itemListElement</uri>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-2</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
      <uri>http://schema.org/itemListElement</uri>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-3</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
      <uri>http://schema.org/itemListElement</uri>
      <uri>https://chasemgrimm.com/publications/research#collection-list-item-4</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Research</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
      <uri>http://schema.org/numberOfItems</uri>
      <typedLiteral datatype="http://www.w3.org/2001/XMLSchema#integer">4</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/ItemList</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-jsonld</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.jsonld</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-jsonld</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>application/ld+json</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-jsonld</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-jsonld</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-n3</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.n3</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-n3</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>text/n3</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-n3</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-n3</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nq</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.nq</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nq</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>application/n-quads</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nq</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nq</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nt</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.nt</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nt</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>application/n-triples</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nt</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nt</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rdf</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.rdf</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rdf</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>application/rdf+xml</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rdf</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rdf</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rj</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.rj</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rj</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>application/rdf+json</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rj</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rj</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trig</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.trig</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trig</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>application/trig</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trig</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trig</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trix</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.trix</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trix</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>application/xml</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trix</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trix</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-ttl</uri>
      <uri>http://schema.org/contentUrl</uri>
      <uri>https://chasemgrimm.com/publications/research.ttl</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-ttl</uri>
      <uri>http://schema.org/encodingFormat</uri>
      <plainLiteral>text/turtle</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-ttl</uri>
      <uri>http://schema.org/provider</uri>
      <uri>https://bighouseenterprise.com/#organization-big-house-enterprise</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-ttl</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/MediaObject</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/about</uri>
      <uri>https://chasemgrimm.com/#person-chase-grimm</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/breadcrumb</uri>
      <uri>https://chasemgrimm.com/publications/research#breadcrumb</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/dateModified</uri>
      <typedLiteral datatype="http://schema.org/Date">2026-09-05T00:00:00+00:00</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/datePublished</uri>
      <typedLiteral datatype="http://schema.org/Date">2025-12-23T00:00:00+00:00</typedLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-jsonld</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-n3</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nq</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-nt</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rdf</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-rj</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trig</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-trix</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/encoding</uri>
      <uri>https://chasemgrimm.com/publications/research#webpage-encoding-ttl</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/image</uri>
      <uri>https://images.bighouseenterprise.com/chase-grimm/chase-grimm/primary/chase-pfp-d045a2.webp</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/inLanguage</uri>
      <plainLiteral>en</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/isPartOf</uri>
      <uri>https://chasemgrimm.com/#website</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/mainEntity</uri>
      <uri>https://chasemgrimm.com/publications/research#collection-list</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/name</uri>
      <plainLiteral>Research</plainLiteral>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://schema.org/url</uri>
      <uri>https://chasemgrimm.com/publications/research</uri>
    </triple>
    <triple>
      <uri>https://chasemgrimm.com/publications/research#webpage</uri>
      <uri>http://www.w3.org/1999/02/22-rdf-syntax-ns#type</uri>
      <uri>http://schema.org/CollectionPage</uri>
    </triple>
  </graph>
  <graph>
    <uri>urn:x-rdflib:default</uri>
  </graph>
</TriX>
