Triple

T4175738
Position Surface form Disambiguated ID Type / Status
Subject Route 129 E86470 entity
Predicate hasDirection P1101 FINISHED
Object Route 129 eastbound E86470 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 129 eastbound | Statement: [Route 129, hasDirection, Route 129 eastbound]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Route 129 eastbound
Context triple: [Route 129, hasDirection, Route 129 eastbound]
  • A. Route 129 chosen
    Route 129 is a state highway in Massachusetts that runs east–west, connecting several communities north of Boston.
  • B. Route 12E
    Route 12E is a historic Lisbon tram line known for its short, scenic loop through the city’s old quarters in traditional yellow trams.
  • C. Route 28E
    Route 28E is a historic Lisbon tram line famed for its vintage yellow trams and scenic route through the city’s oldest and most picturesque neighborhoods.
  • D. U.S. Route 29 Business
    U.S. Route 29 Business is a business loop of U.S. Route 29 that serves local traffic through communities along the main highway corridor.
  • E. Route 24E
    Route 24E is a historic Lisbon tram line known for its classic yellow trams and scenic journey through central neighborhoods.
  • 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_69aed93de98c8190ad838ce507b77c8a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af02e9370481908eda048724261c2b completed March 9, 2026, 5:27 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f564c9c8190bfc321c8ec2dac14 completed March 14, 2026, 3:31 p.m.
Created at: March 9, 2026, 3:45 p.m.