Triple

T19734290
Position Surface form Disambiguated ID Type / Status
Subject Maryland Route 139 E473935 entity
Predicate hasJunctionWith P1018 FINISHED
Object Maryland Route 134 NE NERFINISHED

How this triple was built (3 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: Maryland Route 134 | Statement: [Maryland Route 139, hasJunctionWith, Maryland Route 134]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maryland Route 134
Context triple: [Maryland Route 139, hasJunctionWith, Maryland Route 134]
  • A. Maryland Route 136
    Maryland Route 136 is a state highway in Harford County, Maryland, that runs north–south through rural communities and connects several major routes in the region.
  • B. Maryland Route 135
    Maryland Route 135 is a state highway in western Maryland that connects the town of Oakland to communities along the North Branch Potomac River and nearby recreational areas.
  • C. Maryland Route 130
    Maryland Route 130 is a state highway in Maryland that runs through the Baltimore County suburbs, providing local access and connectivity including to the community of Pikesville.
  • D. Maryland Route 139
    Maryland Route 139 is a state highway in Maryland that runs through Baltimore, serving as a key north–south arterial route connecting central Baltimore with its northern suburbs.
  • E. Maryland Route 146
    Maryland Route 146 is a state highway in Maryland that connects rural northern Baltimore County to the Baltimore metropolitan area and provides access to Interstate 695.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Maryland Route 134
Target entity description: Maryland Route 134 is a short state highway in Maryland that serves local traffic by connecting residential and commercial areas to larger regional routes.
  • A. Maryland Route 136
    Maryland Route 136 is a state highway in Harford County, Maryland, that runs north–south through rural communities and connects several major routes in the region.
  • B. Maryland Route 135
    Maryland Route 135 is a state highway in western Maryland that connects the town of Oakland to communities along the North Branch Potomac River and nearby recreational areas.
  • C. Maryland Route 130
    Maryland Route 130 is a state highway in Maryland that runs through the Baltimore County suburbs, providing local access and connectivity including to the community of Pikesville.
  • D. Maryland Route 139
    Maryland Route 139 is a state highway in Maryland that runs through Baltimore, serving as a key north–south arterial route connecting central Baltimore with its northern suburbs.
  • E. Maryland Route 146
    Maryland Route 146 is a state highway in Maryland that connects rural northern Baltimore County to the Baltimore metropolitan area and provides access to Interstate 695.
  • F. None of above. chosen

Provenance (2 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6515b4d308190af3be1787fa7c65b completed April 20, 2026, 4:16 p.m.
Created at: April 10, 2026, 1:47 p.m.