Triple

T19214084
Position Surface form Disambiguated ID Type / Status
Subject Massachusetts Route 30 E480432 entity
Predicate abbreviation P43 FINISHED
Object Route 30 E220114 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 30 | Statement: [Massachusetts Route 30, abbreviation, Route 30]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Route 30
Context triple: [Massachusetts Route 30, abbreviation, Route 30]
  • A. Route 30 chosen
    Route 30 is a major east–west highway in Massachusetts that serves as a key commercial and commuter corridor through communities such as Framingham.
  • B. Route 30
    Route 30 is a state highway in Connecticut that serves as a regional connector through several towns in the north-central part of the state.
  • C. Route 32
    Route 32 is a state highway in Connecticut that runs generally north–south, serving as a key regional route through several towns and cities.
  • D. Route 32
    Route 32 is a state highway in New York that runs through several communities in the Hudson Valley and central parts of the state.
  • E. Route 32
    Route 32 is a major highway in Costa Rica that connects the capital city of San José with the Caribbean port city of Limón, serving as a key transportation corridor across the country.
  • 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_69d8e8cb8c348190b52075823911c869 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fa397c188190b85bcfd9afd8dce6 completed April 20, 2026, 10:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0700e6af48819092d63922162e3a7b completed May 15, 2026, 11:17 a.m.
Created at: April 10, 2026, 1:22 p.m.