Triple
T22941578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland Route 313 |
E569742
|
entity |
| Predicate | routeDesignation |
P1864
|
FINISHED |
| Object |
MD 313
MD 313 is a state highway on Maryland's Eastern Shore that runs north–south, connecting several small towns and serving as a regional connector between major routes.
|
E1561570
|
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 313 | Statement: [Maryland Route 313, routeDesignation, MD 313]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MD 313 Context triple: [Maryland Route 313, routeDesignation, MD 313]
-
A.
MD 381
MD 381 is a state highway in Maryland that serves as a local connector route in the southern part of the state.
-
B.
MD 373
MD 373 is a state highway in Maryland that serves as a short connector route in Prince George's County.
-
C.
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.
-
D.
MD 322
MD 322 is a short state highway in Maryland that serves as a connector route in the Easton area.
-
E.
MD 223
MD 223 is a state highway in Maryland that serves as a connector route through Prince George's County, linking several local communities and major roads.
- 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 313 Triple: [Maryland Route 313, routeDesignation, MD 313]
Generated description
MD 313 is a state highway on Maryland's Eastern Shore that runs north–south, connecting several small towns and serving as a regional connector between major routes.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: MD 313 Target entity description: MD 313 is a state highway on Maryland's Eastern Shore that runs north–south, connecting several small towns and serving as a regional connector between major routes.
-
A.
MD 381
MD 381 is a state highway in Maryland that serves as a local connector route in the southern part of the state.
-
B.
MD 373
MD 373 is a state highway in Maryland that serves as a short connector route in Prince George's County.
-
C.
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.
-
D.
MD 322
MD 322 is a short state highway in Maryland that serves as a connector route in the Easton area.
-
E.
MD 223
MD 223 is a state highway in Maryland that serves as a connector route through Prince George's County, linking several local communities and major roads.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181394fec81909da791bb346dbd0a |
completed | April 29, 2026, 3:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0bc25492ec81908e8366efa8109791 |
completed | May 19, 2026, 1:52 a.m. |
| NEDg | Description generation | batch_6a0bc2fa53788190bfedeb5bcbfd0876 |
completed | May 19, 2026, 1:55 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0bc3c11ebc8190995c0025a594d40a |
completed | May 19, 2026, 1:58 a.m. |
Created at: April 17, 2026, 3:45 p.m.