Triple
T19742389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 261 |
E474158
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 261 |
E1240341
|
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 261 | Statement: [Maine State Route 261, abbreviation, SR 261]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 261 Context triple: [Maine State Route 261, abbreviation, SR 261]
-
A.
SR 261
chosen
SR 261 is a state highway in the United States designated as State Route 261.
-
B.
SR 267
SR 267 is a California state highway that connects the Lake Tahoe area near Kings Beach with the town of Truckee, providing access over the Sierra Nevada.
-
C.
SR 267
SR 267 is a state highway in Maine that serves as a short connector route within the state's regional road network.
-
D.
SR 268
SR 268 is a state highway in Maine that serves as a short connector route within the state's regional road network.
-
E.
SR 26
SR 26 is a state highway in Washington that runs east–west across the state’s central agricultural region, connecting small rural communities and major 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65162382081909bd5a251d7da7f75 |
completed | April 20, 2026, 4:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07b4fd89488190a1d3b7e43f37e46f |
completed | May 16, 2026, 12:06 a.m. |
Created at: April 10, 2026, 1:47 p.m.