Triple
T18957027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama State Route 167 |
E463806
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 167 |
—
|
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 167 | Statement: [Alabama State Route 167, abbreviation, SR 167]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 167 Context triple: [Alabama State Route 167, abbreviation, SR 167]
-
A.
SR 167
chosen
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
B.
SR 165
SR 165 is a state highway in Maine that serves as a regional connector route between several communities in the northern part of the state.
-
C.
SR 166
SR 166 is a state highway in Georgia that serves as a major east–west transportation corridor through the Atlanta metropolitan area and surrounding regions.
-
D.
SR 163
SR 163 is a major north–south freeway in San Diego, California, connecting downtown with the inland freeway network and passing through Balboa Park.
-
E.
SR 162
SR 162 is a state highway in Indiana that serves as a regional connector route through several southern Indiana communities.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5cee8348190b6506b10aed6c58a |
completed | April 20, 2026, 7:29 a.m. |
Created at: April 10, 2026, noon