Triple
T11970846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 155 |
E284914
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 155 |
E576362
|
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 155 | Statement: [Maine State Route 155, abbreviation, SR 155]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 155 Context triple: [Maine State Route 155, 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 151
SR 151 is a state highway in Maine that runs through rural communities, connecting local roads to larger regional routes.
-
C.
SR 15
SR 15 is a state highway in Maine that runs through the city of Brewer and connects several communities in the region.
-
D.
SR 152
SR 152 is a state highway in Maine that runs generally north–south, connecting several rural communities and serving as a regional connector route.
-
E.
SR 115
SR 115 is a state highway in Maine that serves as a regional connector route between several communities in the southern part of the state.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037d32e88190b1509285dc907d29 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48a9628cc819095d15fd90023e57d |
completed | May 1, 2026, 11:12 a.m. |
Created at: April 8, 2026, 9:46 p.m.