Triple

T324366
Position Surface form Disambiguated ID Type / Status
Subject Route 25 (via Route 28 connection) E6480 entity
Predicate hasConnection P8776 FINISHED
Object Route 28 E15824 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 28 | Statement: [Route 25 (via Route 28 connection), hasConnection, Route 28]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route 28
Context triple: [Route 25 (via Route 28 connection), hasConnection, Route 28]
  • A. Route 28 chosen
    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 34
    Route 34 is a SEPTA subway–surface trolley line in Philadelphia that runs between Center City and West Philadelphia.
  • C. Route 36
    Route 36 is a SEPTA subway–surface trolley line in Philadelphia that provides light rail service between Center City and Southwest Philadelphia.
  • D. Route 107
    Route 107 is a state highway in Massachusetts that runs through cities such as Revere and Lynn, serving as a key north–south arterial route north of Boston.
  • E. Route 99
    Route 99 is a state highway in Massachusetts that runs north of Boston, serving as a key urban connector through cities such as Everett and Malden.
  • 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_69a2e7933d6c8190bb2592ad13286ef2 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2ea941b108190983ec543569e580e completed Feb. 28, 2026, 1:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3fe8dde4c8190bd897e5251eb6941 completed March 1, 2026, 8:53 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.