Triple

T8510627
Position Surface form Disambiguated ID Type / Status
Subject Marystown E201442 entity
Predicate roadAccessVia P9041 FINISHED
Object Route 220 E671802 NE FINISHED

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: Route 220 | Statement: [Marystown, roadAccessVia, Route 220]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route 220
Context triple: [Marystown, roadAccessVia, Route 220]
  • A. Route 28
    Route 28 is a major north–south state highway in Massachusetts that runs from the Cape Cod area through Boston and into New Hampshire, serving as a key regional arterial road.
  • B. Route 254
    Route 254 is a state highway in Connecticut that serves as a connector route through Litchfield County, linking several local communities and major roads.
  • C. Route 520 chosen
    Route 520 is a provincial highway in Labrador, Canada, that serves as a spur of the Trans-Labrador Highway connecting it to nearby communities.
  • D. Route 129
    Route 129 is a state highway in Massachusetts that runs east–west, connecting several communities north of Boston.
  • E. Route 64
    Route 64 is a Chilean roadway that serves as a key regional connector in the Valparaíso area, linking the inland city of Quilpué with surrounding localities and major routes.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca8320e5748190ac2c585a0bba8193 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe608e5b08190a6d551793e8ed94b completed March 31, 2026, 3:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce6d2eef208190b505a64d01f656f4 completed April 2, 2026, 1:20 p.m.
Created at: March 30, 2026, 6:15 p.m.