Triple
T22631313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 22 (Alabama) |
E558559
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 22 |
—
|
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 22 | Statement: [SR 22 (Alabama), abbreviation, SR 22]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 22 Context triple: [SR 22 (Alabama), abbreviation, SR 22]
-
A.
SR 22
SR 22 is a state highway in Florida that serves the Callaway area, providing a key route for local and regional traffic.
-
B.
SR 22
chosen
SR 22 is a state highway in Alabama that runs east–west across the central part of the state, connecting several rural communities and small towns.
-
C.
SR 222
SR 222 is a state highway in Maine that connects the city of Bangor with the town of Corinna.
-
D.
SR 220
SR 220 is a state highway in Maine that runs through several rural communities, connecting local roads and other major routes in the region.
-
E.
SR 221
SR 221 is a state highway in Maine that serves as a short connector route between local communities and larger regional roads.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17009ecb0819082f94505b0e2c5b8 |
completed | April 29, 2026, 2:42 a.m. |
Created at: April 17, 2026, 3:02 p.m.