Triple

T4441542
Position Surface form Disambiguated ID Type / Status
Subject Boston beltway system E95781 entity
Predicate hasComponent P35 FINISHED
Object Route 128 E27590 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 128 | Statement: [Boston beltway system, hasComponent, Route 128]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route 128
Context triple: [Boston beltway system, hasComponent, Route 128]
  • A. Route 128 chosen
    Route 128 is a major circumferential highway around the Boston metropolitan area in Massachusetts, historically known as a key technology corridor.
  • B. State Route 128
    State Route 128 is a state highway in Maine that serves as a regional connector route in and around Woolwich.
  • C. Route 495
    Route 495 is a major east–west highway in northern New Jersey that serves as a key connector between the New Jersey Turnpike and the Lincoln Tunnel into Manhattan.
  • D. Massachusetts Route 129
    Massachusetts Route 129 is a state highway in northeastern Massachusetts that runs through several North Shore communities, including the city of Lynn.
  • E. Massachusetts Route 111
    Massachusetts Route 111 is a state highway in Massachusetts that runs generally northwest–southeast, linking several suburban communities to larger regional routes and interstates.
  • 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_69b3453ea2b48190a26f154b3b8fece5 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b355ad71588190b1dcad4250472c29 completed March 13, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69b61380fca08190bf036a7d82cee0e7 completed March 15, 2026, 2:03 a.m.
Created at: March 12, 2026, 11:32 p.m.