Triple

T8337429
Position Surface form Disambiguated ID Type / Status
Subject Fairborn, Ohio E195822 entity
Predicate servedByHighway P385 FINISHED
Object State Route 444 E723860 NE 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: State Route 444 | Statement: [Fairborn, Ohio, servedByHighway, State Route 444]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: State Route 444
Context triple: [Fairborn, Ohio, servedByHighway, State Route 444]
  • A. State Route 444 chosen
    State Route 444 is a state highway in Ohio that serves as a key local connector route in and around Beavercreek.
  • B. State Route 44
    State Route 44 is a numbered state highway in Queensland, Australia, that includes the scenic coastal Captain Cook Highway as part of its route.
  • C. State Route 45
    State Route 45 is a north–south state highway in California’s Sacramento Valley that runs through rural agricultural communities, including Colusa County.
  • D. State Route 540
    State Route 540 is an Ohio state highway that serves as a local connector route in and around Bellefontaine in Logan County.
  • E. State Route 43
    State Route 43 is a north–south state highway in California’s San Joaquin Valley that connects several agricultural communities between Bakersfield and Selma.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca82ecbdc481908a55cad8ca062d88 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fd5027c81909724f25aa30bbe58 completed March 31, 2026, 8:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd95e17300819090e405c4c60b280d completed April 1, 2026, 10:02 p.m.
Created at: March 30, 2026, 5:57 p.m.