Triple
T7022233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR-143 |
E162854
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 143 |
E162853
|
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 143 | Statement: [SR-143, abbreviation, SR 143]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 143 Context triple: [SR-143, abbreviation, SR 143]
-
A.
SR 143
chosen
SR 143 is a short Arizona state highway in the Phoenix metropolitan area that primarily serves as a connector between Interstate 10 and Phoenix Sky Harbor International Airport.
-
B.
SR 14
SR 14 is a state highway in Georgia that serves as a key transportation route connecting several communities in the western part of the state.
-
C.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
-
D.
SR 134
SR 134 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
E.
SR 124
SR 124 is a state highway in Georgia that serves as an important regional connector through several suburban and semi-rural communities northeast of Atlanta.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e1ec34a48190b64cafb94e2f8706 |
completed | March 27, 2026, 8 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7757c87788190b09ced669b5c4d83 |
completed | March 28, 2026, 6:30 a.m. |
Created at: March 27, 2026, 2:35 p.m.