Triple

T17073257
Position Surface form Disambiguated ID Type / Status
Subject Rhode Island Route 138 E414275 entity
Predicate abbreviation P43 FINISHED
Object Route 138 E600212 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: Route 138 | Statement: [Rhode Island Route 138, abbreviation, Route 138]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route 138
Context triple: [Rhode Island Route 138, abbreviation, Route 138]
  • A. Route 138 chosen
    Route 138 is a major provincial highway in Quebec that runs along the north shore of the Saint Lawrence River, connecting numerous communities including Sainte-Anne-de-Beaupré.
  • B. Route 136
    Route 136 is a state highway in southwestern Connecticut that runs through coastal communities and connects several local and regional routes.
  • C. Route 136
    Route 136 is an urban highway in Montreal that serves as a key east–west connector through the city’s central road network.
  • D. Route 132
    Route 132 is a major commercial roadway in Hyannis, Massachusetts, serving as a key access route to shopping centers and businesses on Cape Cod.
  • E. Route 131
    Route 131 is a provincial highway in Quebec, Canada, that serves as a key north–south transportation corridor through the Lanaudière region.
  • 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_69d886cef44c8190ba56c44b4e863e64 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbc28fec81909c39d432094d9cdd completed April 18, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a012ede108881909ddd0455be53ffac completed May 11, 2026, 1:20 a.m.
Created at: April 10, 2026, 5:34 a.m.