Triple
T8978861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 121 |
E214468
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 121 |
E641849
|
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 121 | Statement: [Maine State Route 121, abbreviation, SR 121]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 121 Context triple: [Maine State Route 121, abbreviation, SR 121]
-
A.
SR 121
chosen
SR 121 is a state highway in California that runs through Sonoma and Napa counties, serving as a key route to the Napa Valley wine region.
-
B.
SR 12
SR 12 is a state highway in Florida that serves as an important regional route connecting small communities in the state's Panhandle.
-
C.
SR 112
SR 112 is a state highway in Maine that serves as a regional connector route between several communities in the southern part of the state.
-
D.
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.
-
E.
SR 111
SR 111 is a state highway in Maine that runs east–west, connecting the city of Biddeford to the town of Alfred and serving as an important regional route in York County.
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a4b3e88190b778a9b5589cab6d |
completed | April 1, 2026, 12:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfd0afe9688190bdd66198ab31c2c7 |
completed | April 3, 2026, 2:37 p.m. |
Created at: March 30, 2026, 7:03 p.m.