Triple
T15424157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road 26 |
E369460
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 26 |
E975597
|
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: SR 26 | Statement: [State Road 26, abbreviation, SR 26]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 26 Context triple: [State Road 26, abbreviation, SR 26]
-
A.
SR 26
chosen
SR 26 is a state highway in Washington that runs east–west across the state’s central agricultural region, connecting small rural communities and major routes.
-
B.
SR 267
SR 267 is a California state highway that connects the Lake Tahoe area near Kings Beach with the town of Truckee, providing access over the Sierra Nevada.
-
C.
SR 269
SR 269 is a short state highway in Florida that serves local traffic in the state's northern region.
-
D.
SR 265
SR 265 is a short Nevada state highway that connects the town of Silver Peak to U.S. Route 6 in Esmeralda County.
-
E.
SR 266
SR 266 is a state highway in Georgia that serves as a regional connector route within the state's road network.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec032548190840b558dde6057c7 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a7ed0ec8190b8086f78df965b61 |
completed | May 9, 2026, 11:29 a.m. |
Created at: April 10, 2026, 3:20 a.m.