Triple
T11743367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 143 |
E279208
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 143 |
E907837
|
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: [State Route 143, abbreviation, SR 143]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 143 Context triple: [State Route 143, abbreviation, SR 143]
-
A.
SR 143
chosen
SR 143 is a state highway in Maine that serves as a regional connector route between local communities.
-
B.
SR 143
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.
-
C.
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.
-
D.
SR 14
SR 14 is a major north–south California state highway connecting Los Angeles to the high desert and serving as a key route through the Antelope Valley.
-
E.
SR 14
SR 14 is a state highway in Washington that runs along the Columbia River in the southern part of the state, serving as an important east–west transportation corridor.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f191388190bd6ef7e80c41ca48 |
completed | April 10, 2026, 7:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f0902f8c448190a71512353788ef09 |
completed | April 28, 2026, 10:47 a.m. |
Created at: April 8, 2026, 9:41 p.m.