Triple

T20601497
Position Surface form Disambiguated ID Type / Status
Subject Maryland Route 121 E506191 entity
Predicate connectsTo P845 FINISHED
Object MD 355 NE NERFINISHED

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 355 | Statement: [Maryland Route 121, connectsTo, MD 355]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MD 355
Context triple: [Maryland Route 121, connectsTo, MD 355]
  • A. MD 355 chosen
    MD 355 is a major state highway in Maryland that runs through Montgomery County and serves as a key commercial and commuter corridor, including the stretch known as Rockville Pike.
  • B. MD 322
    MD 322 is a short state highway in Maryland that serves as a connector route in the Easton area.
  • C. 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.
  • D. MD 450
    MD 450 is a state highway in Maryland that serves as an important east–west route connecting communities in the Annapolis and Washington, D.C. metropolitan areas.
  • 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.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b4ba6ae88190af871e1f9522c704 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aa1ffd088190adeacb9fe4907530 completed April 20, 2026, 10:35 p.m.
Created at: April 16, 2026, 11:41 a.m.