Triple
T14135740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road 21 |
E350288
|
entity |
| Predicate | hasRouteDesignation |
P5539
|
FINISHED |
| Object | SR 21 |
unclear NED1
|
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 21 | Statement: [State Road 21, hasRouteDesignation, SR 21]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 21 Context triple: [State Road 21, hasRouteDesignation, SR 21]
-
A.
SR 21
SR 21 is a primary state highway in Alabama that runs north–south across the state, connecting several major towns and highways.
-
B.
SR 21
SR 21 is a Florida state highway that runs through the Jacksonville area, serving as a major north–south route connecting suburban communities and military installations.
-
C.
SR 210
SR 210 is a major California state highway forming part of the Foothill Freeway corridor across the Greater Los Angeles and Inland Empire regions.
-
D.
SR 219
SR 219 is a state highway in Georgia that serves as a regional connector route through west-central parts of the state.
-
E.
SR 219
SR 219 is a state highway in Alabama that serves as a regional connector route through several central and western counties.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610e949c8190852d336c9d12bfd0 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd193728d88190acdb08ad0cf8b394 |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 12:13 a.m.