Triple
T13739204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine State Route 180 |
E330034
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 180 |
E279582
|
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 180 | Statement: [Maine State Route 180, abbreviation, SR 180]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 180 Context triple: [Maine State Route 180, abbreviation, SR 180]
-
A.
SR 180
chosen
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
B.
SR 188
SR 188 is a state highway in Ohio that connects several communities in the central part of the state.
-
C.
SR 188
SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
-
D.
SR 18
SR 18 is a state highway in Georgia that runs east–west across the central part of the state, connecting several small towns and regional routes.
-
E.
SR 182
SR 182 is a state highway designated as State Route 182 within a U.S. state’s numbered road network.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0204d50c8190a5413cc9a1b26e14 |
completed | April 14, 2026, 8:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7a84dbdc48190a4724bb9c3523b25 |
completed | May 3, 2026, 7:55 p.m. |
Created at: April 9, 2026, 9:55 p.m.