Triple

T22381745
Position Surface form Disambiguated ID Type / Status
Subject US 151 E553290 entity
Predicate partlyConcurrentWith P15900 FINISHED
Object US 30 NE NERFINISHED

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: US 30 | Statement: [US 151, partlyConcurrentWith, US 30]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: US 30
Context triple: [US 151, partlyConcurrentWith, US 30]
  • A. US 30 chosen
    US 30 is a major east–west U.S. Highway that stretches from the East Coast to the West, serving as a key transportation corridor across multiple states.
  • B. US 35
    US 35 is a United States Numbered Highway running generally northwest–southeast through the Midwest and Appalachia, connecting cities such as Dayton, Ohio, and Charleston, West Virginia.
  • C. US 31
    US 31 is a major north–south United States highway running through several Midwestern and Southern states, serving as an important regional transportation corridor.
  • D. US 23
    US 23 is a major north–south United States highway running from Florida to Michigan, serving as an important regional transportation corridor.
  • E. US 29
    US 29 is a major north–south U.S. Highway running through the eastern United States, connecting cities from Florida to Virginia and beyond.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1582cce608190b5324b30f349a3ff completed April 29, 2026, 1 a.m.
Created at: April 16, 2026, 8:45 p.m.