Triple
T21620443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 219 (Alabama) |
E533560
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 219 |
—
|
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: SR 219 | Statement: [SR 219 (Alabama), abbreviation, SR 219]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 219 Context triple: [SR 219 (Alabama), abbreviation, SR 219]
-
A.
SR 219
SR 219 is a state highway in Georgia that serves as a regional connector route through west-central parts of the state.
-
B.
SR 219
chosen
SR 219 is a state highway in Alabama that serves as a regional connector route through several central and western counties.
-
C.
SR 219
SR 219 is a state highway in Maine that runs through rural communities, connecting several small towns in the western part of the state.
-
D.
SR 218
SR 218 is a state highway in Maine that runs through Lincoln County, connecting several small towns and rural areas.
-
E.
SR 215
SR 215 is a state highway in Alabama that serves as a primary route through the city of Tuscaloosa, connecting several major roads and local destinations.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3baeeae48190b78583b3bec8ee33 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 16, 2026, 6:34 p.m.