Triple
T20601492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland Route 121 |
E506191
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
MD 121
MD 121 is a state highway in Maryland that serves as a local connector route in Montgomery County.
|
E1439575
|
NE FINISHED |
How this triple was built (4 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 121 | Statement: [Maryland Route 121, abbreviation, MD 121]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MD 121 Context triple: [Maryland Route 121, abbreviation, MD 121]
-
A.
MD 212
MD 212 is a Maryland state highway serving as a key east–west arterial route in the Washington, D.C. metropolitan area, connecting communities in Prince George’s and Montgomery counties.
-
B.
MD 145
MD 145 is a state highway in Maryland that serves as an east–west route connecting communities in Baltimore County.
-
C.
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.
-
D.
MD 147
MD 147 is a state highway in Maryland that runs between Baltimore and Harford counties, serving as a key commuter route in the region.
-
E.
MD 210
MD 210 is a major state highway in Maryland that runs from the Washington, D.C. area toward Indian Head, serving as a key commuter and commercial route in Prince George’s and Charles counties.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: MD 121 Triple: [Maryland Route 121, abbreviation, MD 121]
Generated description
MD 121 is a state highway in Maryland that serves as a local connector route in Montgomery County.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MD 121 Target entity description: MD 121 is a state highway in Maryland that serves as a local connector route in Montgomery County.
-
A.
MD 212
MD 212 is a Maryland state highway serving as a key east–west arterial route in the Washington, D.C. metropolitan area, connecting communities in Prince George’s and Montgomery counties.
-
B.
MD 145
MD 145 is a state highway in Maryland that serves as an east–west route connecting communities in Baltimore County.
-
C.
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.
-
D.
MD 147
MD 147 is a state highway in Maryland that runs between Baltimore and Harford counties, serving as a key commuter route in the region.
-
E.
MD 210
MD 210 is a major state highway in Maryland that runs from the Washington, D.C. area toward Indian Head, serving as a key commuter and commercial route in Prince George’s and Charles counties.
- F. None of above. chosen
Provenance (5 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1ffd088190adeacb9fe4907530 |
completed | April 20, 2026, 10:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08b3f35cb08190a7cdc354534fba1c |
completed | May 16, 2026, 6:14 p.m. |
| NEDg | Description generation | batch_6a08b4c5946081909ac59ed47f3ba909 |
completed | May 16, 2026, 6:17 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a08b53450a481909133bd18c34dc78c |
completed | May 16, 2026, 6:19 p.m. |
Created at: April 16, 2026, 11:41 a.m.