Triple

T18396793
Position Surface form Disambiguated ID Type / Status
Subject Ohio State Route 58 E449890 entity
Predicate terminusSouth P1866 FINISHED
Object Ashland, Ohio NE NERFINISHED

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: Ashland, Ohio | Statement: [Ohio State Route 58, terminusSouth, Ashland, Ohio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ashland, Ohio
Context triple: [Ohio State Route 58, terminusSouth, Ashland, Ohio]
  • A. Ashland, Ohio chosen
    Ashland, Ohio is a small city in north-central Ohio known historically as a regional manufacturing and agricultural center and home to Ashland University.
  • B. Ashland
    Ashland is an unincorporated community in Alameda County, California, situated in the East Bay region of the San Francisco Bay Area.
  • C. Ashland
    Ashland is a Chicago 'L' rapid transit station on the CTA's Pink Line serving the city's Near West Side.
  • D. Ashland
    Ashland is a small town in northern Mississippi that serves as the administrative and cultural center of Benton County.
  • E. Ashland
    Ashland is a small borough in Schuylkill County, Pennsylvania, historically known for its anthracite coal mining heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9fab8a8819086a9ddc0871715e0 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e5184777548190818365ee52ac88b7 completed April 19, 2026, 6 p.m.
Created at: April 10, 2026, 10:46 a.m.