Triple
T17220374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road 112 |
E417962
|
entity |
| Predicate | signedAs |
P11811
|
FINISHED |
| Object | SR 112 |
E751986
|
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 112 | Statement: [State Road 112, signedAs, SR 112]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 112 Context triple: [State Road 112, signedAs, SR 112]
-
A.
SR 112
chosen
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.
-
B.
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.
-
C.
SR 111
SR 111 is a major north–south state highway in Southern California that runs through the Coachella and Imperial Valleys, connecting desert communities and serving as a key regional route.
-
D.
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.
-
E.
SR 117
SR 117 is a state highway in Maine that runs through several counties, connecting multiple rural towns and regional routes.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddd52d4819098b51d55e063c8ab |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a016757985881909b5711eb1f206cd7 |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:38 a.m.