Triple

T22381741
Position Surface form Disambiguated ID Type / Status
Subject US 151 E553290 entity
Predicate partlyConcurrentWith P15900 FINISHED
Object US 20 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 20 | Statement: [US 151, partlyConcurrentWith, US 20]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: US 20
Context triple: [US 151, partlyConcurrentWith, US 20]
  • A. US 20 chosen
    US 20 is a major east–west United States highway that stretches from the Pacific Northwest to New England, serving as one of the country’s longest transcontinental routes.
  • B. US 202
    US 202 is a U.S. highway running through the northeastern United States, connecting cities in states such as Delaware, Pennsylvania, New Jersey, New York, and beyond.
  • C. US 201
    US 201 is a U.S. highway in Maine that runs north–south from Brunswick to the Canadian border, serving as a key route through the state's interior.
  • D. US 2
    US 2 is a major east–west U.S. highway that runs across the northern United States, roughly parallel to the Canadian border.
  • E. US 1
    US 1 is a major north–south U.S. highway running along the East Coast, serving as a key route through numerous states and cities from Florida to Maine.
  • 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.