Triple

T20550811
Position Surface form Disambiguated ID Type / Status
Subject Missouri lettered route system E504590 entity
Predicate hasRouteExample P1259 FINISHED
Object Route BB 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: Route BB | Statement: [Missouri lettered route system, hasRouteExample, Route BB]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route BB
Context triple: [Missouri lettered route system, hasRouteExample, Route BB]
  • A. Route BB chosen
    Route BB is a state-maintained secondary highway in Missouri, designated with the lettered route name "BB."
  • B. Route 55
    Route 55 is a major limited-access highway in southern New Jersey that serves as a key commuter and regional connector through Gloucester County and surrounding areas.
  • C. Route 52
    Route 52 is a metro line in Amsterdam that forms part of the city’s North–South Line, connecting the northern and southern districts through the city center.
  • D. Route 52
    Route 52 is a numbered roadway that serves as a regional connector route intersecting with Provincial Trunk Highway 101.
  • E. Route 52
    Route 52 is a rural highway in New Zealand that links several small communities in the lower North Island.
  • 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_69e0b4b52c048190952b4d0f430813a3 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5d8b55081909c3e3e972aff846d completed April 20, 2026, 10:16 p.m.
Created at: April 16, 2026, 11:38 a.m.