Triple
T14695720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland Route 373 |
E345150
|
entity |
| Predicate | routeDesignation |
P1864
|
FINISHED |
| Object |
MD 373
MD 373 is a state highway in Maryland that serves as a short connector route in Prince George's County.
|
E1114121
|
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 373 | Statement: [Maryland Route 373, routeDesignation, MD 373]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MD 373 Context triple: [Maryland Route 373, routeDesignation, MD 373]
-
A.
MD 33
MD 33 is a state highway in Maryland that runs through Talbot County, connecting the town of Easton with several communities along the Miles River and Chesapeake Bay.
-
B.
MD 3
MD 3 is a primary state highway in Maryland that connects the Baltimore–Washington Parkway area to the U.S. Route 50/301 corridor near Bowie.
-
C.
MD 32
MD 32 is a state highway in Maryland that serves as a major east–west and north–south connector through the central part of the state, linking suburbs, military installations, and key regional routes.
-
D.
MD 322
MD 322 is a short state highway in Maryland that serves as a connector route in the Easton area.
-
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. 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 373 Triple: [Maryland Route 373, routeDesignation, MD 373]
Generated description
MD 373 is a state highway in Maryland that serves as a short connector route in Prince George's County.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MD 373 Target entity description: MD 373 is a state highway in Maryland that serves as a short connector route in Prince George's County.
-
A.
MD 33
MD 33 is a state highway in Maryland that runs through Talbot County, connecting the town of Easton with several communities along the Miles River and Chesapeake Bay.
-
B.
MD 3
MD 3 is a primary state highway in Maryland that connects the Baltimore–Washington Parkway area to the U.S. Route 50/301 corridor near Bowie.
-
C.
MD 32
MD 32 is a state highway in Maryland that serves as a major east–west and north–south connector through the central part of the state, linking suburbs, military installations, and key regional routes.
-
D.
MD 322
MD 322 is a short state highway in Maryland that serves as a connector route in the Easton area.
-
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. 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58855e081908b38f9515db5677f |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fde18e279c8190814f90e947734541 |
completed | May 8, 2026, 1:13 p.m. |
| NEDg | Description generation | batch_69fde259ea5881909d48031a183ca614 |
completed | May 8, 2026, 1:17 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fde2d0445881908b17fc24369ee90f |
completed | May 8, 2026, 1:19 p.m. |
Created at: April 10, 2026, 1:28 a.m.