Triple

T23211089
Position Surface form Disambiguated ID Type / Status
Subject Route 123 bridge at Occoquan E580595 entity
Predicate hasNameElement P3097 FINISHED
Object Route 123 — 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 123 | Statement: [Route 123 bridge at Occoquan, hasNameElement, Route 123]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Route 123
Context triple: [Route 123 bridge at Occoquan, hasNameElement, Route 123]
  • A. Route 123 chosen
    Route 123 is a state highway in Massachusetts that runs east–west across the southeastern part of the state, connecting several cities and towns between Rhode Island and the South Shore.
  • B. Route 124
    Route 124 is a state highway in Massachusetts that runs through parts of Cape Cod, connecting the towns of Harwich and Brewster.
  • C. Route 125
    Route 125 is a state highway in northeastern Massachusetts that runs through several communities north of Boston, serving as a key regional connector.
  • D. Route 129
    Route 129 is a state highway in Massachusetts that runs east–west, connecting several communities north of Boston.
  • E. Route 122
    Route 122 is a state highway in Maine that serves as a short connector route between the cities of Auburn and New Gloucester.
  • 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_69e24602ae1481908aaa6bc7ca493867 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f191614bc4819080938752d843dcc6 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:07 p.m.