Triple

T8858320
Position Surface form Disambiguated ID Type / Status
Subject Missouri Route O E210818 entity
Predicate abbreviation P43 FINISHED
Object MO Route O E210818 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: MO Route O | Statement: [Missouri Route O, abbreviation, MO Route O]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MO Route O
Context triple: [Missouri Route O, abbreviation, MO Route O]
  • A. Ohechi route
    The Ohechi route is a coastal section of Japan’s historic Kumano Kodo pilgrimage network, running along the southern edge of the Kii Peninsula and linking ancient sacred sites.
  • B. Missouri Route O chosen
    Missouri Route O is a state secondary highway in Missouri that serves as a local connector route in and around the city of Fulton.
  • C. Route 185
    Route 185 is a numbered roadway that serves as a connector within the regional highway network linked to Route 440.
  • D. Route 1A
    Route 1A is a state highway in Massachusetts that runs along the North Shore and provides access to Logan International Airport and coastal communities near Boston.
  • E. Route 3
    Route 3 is a major Costa Rican highway that passes through the district of Uruca and connects key urban areas in the country’s Central Valley.
  • 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_69ca838bbddc8190ab546d737e5d350f completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60e3b62c8190bf779e7e1db767f6 completed April 1, 2026, 12:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfa0b1b86481909ec0b78de043d8f8 completed April 3, 2026, 11:12 a.m.
Created at: March 30, 2026, 6:50 p.m.