Triple
T16182677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland Route 189 |
E392722
|
entity |
| Predicate | roadDesignation |
P1019
|
FINISHED |
| Object | MD 189 |
E1199324
|
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: MD 189 | Statement: [Maryland Route 189, roadDesignation, MD 189]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MD 189 Context triple: [Maryland Route 189, roadDesignation, MD 189]
-
A.
MD 189
chosen
MD 189 is a state highway in Maryland that primarily serves the Bethesda area, connecting local roads to major routes and facilitating suburban commuter traffic.
-
B.
MD 458
MD 458 is a state highway in Maryland that serves as a short connector route through suburban communities in Prince George's County.
-
C.
MD 145
MD 145 is a state highway in Maryland that serves as an east–west route connecting communities in Baltimore County.
-
D.
MD 214
MD 214 is a major east–west state highway in Maryland that connects Washington, D.C. suburbs with communities in Prince George’s and Anne Arundel counties.
-
E.
MD 381
MD 381 is a state highway in Maryland that serves as a local connector route 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205ef39081908da383abdebc2ccc |
completed | April 17, 2026, 11:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0007899b408190abcb7e72bdc81e9d |
completed | May 10, 2026, 4:20 a.m. |
Created at: April 10, 2026, 5:02 a.m.