Triple
T13739432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Route 149 |
E330041
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | Route 149 |
E930743
|
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: Route 149 | Statement: [New York State Route 149, abbreviation, Route 149]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Route 149 Context triple: [New York State Route 149, abbreviation, Route 149]
-
A.
Route 149
chosen
Route 149 is a state highway in Maine that serves as a regional connector between several small communities.
-
B.
Route 145
Route 145 is a state highway in Maine that serves as a local connector route through Franklin County.
-
C.
Route 140
Route 140 is a state highway in Massachusetts that runs generally north–south, connecting several cities and towns between New Bedford and the Franklin area.
-
D.
Route 146
Route 146 is a major north–south highway in Massachusetts and Rhode Island that connects the Worcester area to the Providence metropolitan region.
-
E.
Route 147
Route 147 is a numbered roadway that serves as a key connector passing through the Uruca area.
- 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_69f79d6bce9881909209231f6dfcf9bf |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.