Triple
T8216974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 21 (Alabama) |
E191956
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 21 |
E191956
|
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: [SR 21 (Alabama), abbreviation, SR 21]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 21 Context triple: [SR 21 (Alabama), abbreviation, SR 21]
-
A.
SR 21
chosen
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 219
SR 219 is a state highway in Georgia that serves as a regional connector route through west-central parts of the state.
-
D.
SR 219
SR 219 is a state highway in Alabama that serves as a regional connector route through several central and western counties.
-
E.
SR 121
SR 121 is a state highway in California that runs through Sonoma and Napa counties, serving as a key route to the Napa Valley wine 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb776f41108190bed1c6a8ddbea374 |
completed | March 31, 2026, 7:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd34c010b48190b564fd365a5304d1 |
completed | April 1, 2026, 3:07 p.m. |
Created at: March 30, 2026, 5:44 p.m.