Triple

T25464751
Position Surface form Disambiguated ID Type / Status
Subject In-Use Off-Road Diesel-Fueled Fleets Regulation E638142 entity
Predicate complianceStrategy P75623 FINISHED
Object engine replacement LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: engine replacement | Statement: [In-Use Off-Road Diesel-Fueled Fleets Regulation, complianceStrategy, engine replacement]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: complianceStrategy
Context triple: [In-Use Off-Road Diesel-Fueled Fleets Regulation, complianceStrategy, engine replacement]
  • A. complianceApproach chosen
    Indicates the method or strategy an entity uses to meet, adhere to, or enforce specified rules, standards, or regulatory requirements.
  • B. complianceUse
    Indicates that something is used, implemented, or behaves in accordance with a specified rule, standard, or compliance requirement.
  • C. conformanceStyle
    Indicates the specific manner, pattern, or set of rules by which something adheres to or complies with a given standard or specification.
  • D. indicatesComplianceWith
    Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
  • E. complianceEnforcedBy
    Indicates that adherence to a rule, standard, or requirement is ensured or compelled by a specified enforcing entity.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69e75db8bab08190baca80b4a8c315fd completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f72f1a788190904ed62ebdccc57c completed May 2, 2026, 1:07 p.m.
PD Predicate disambiguation batch_69f5afd5baac8190bb8ed576813c8591 completed May 2, 2026, 8:03 a.m.
Created at: April 21, 2026, 2:14 p.m.