Triple
T23112665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 155 (Alabama) |
E576362
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 155 |
—
|
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 155 | Statement: [SR 155 (Alabama), abbreviation, SR 155]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 155 Context triple: [SR 155 (Alabama), abbreviation, SR 155]
-
A.
SR 155
chosen
SR 155 is a state highway in Alabama that serves as a connector route within the state's road network.
-
B.
SR 155
SR 155 is a state highway in Washington that connects the Grand Coulee Dam area with U.S. Route 2 near Coulee City, passing through several small communities in central Washington.
-
C.
SR 155
SR 155 is a state highway in Georgia that runs through the Atlanta metropolitan area, connecting several suburbs and local communities.
-
D.
SR 151
SR 151 is a state highway in Maine that runs through rural communities, connecting local roads to larger regional routes.
-
E.
SR 151
SR 151 is a state highway in Ohio that serves as a regional connector route through the eastern part of the state.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e100d408190a7349563235640d5 |
completed | April 29, 2026, 4:50 a.m. |
Created at: April 17, 2026, 3:58 p.m.