Triple

T20242968
Position Surface form Disambiguated ID Type / Status
Subject SH 233 E498344 entity
Predicate connectsTo P845 FINISHED
Object U.S. Route 50 Business 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: U.S. Route 50 Business | Statement: [SH 233, connectsTo, U.S. Route 50 Business]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: U.S. Route 50 Business
Context triple: [SH 233, connectsTo, U.S. Route 50 Business]
  • A. U.S. Route 50 Business chosen
    U.S. Route 50 Business is a business loop of U.S. Route 50 that serves local traffic and commercial areas in and around Pueblo, Colorado.
  • B. U.S. Route 54 Business
    U.S. Route 54 Business is a business loop of U.S. Route 54 that serves local traffic and commercial areas in Quay County, New Mexico.
  • C. U.S. Route 15 Business
    U.S. Route 15 Business is a business route of U.S. Route 15 that serves local traffic through the city of Frederick, Maryland.
  • D. U.S. Route 50A
    U.S. Route 50A is an alternate alignment of U.S. Route 50 in Nevada that serves as a major east–west highway through communities such as Fernley.
  • E. U.S. Route 250 Business
    U.S. Route 250 Business is a business loop of U.S. Route 250 that serves local traffic and commercial areas along the highway’s corridor.
  • 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_69da6274c58c81909c646eabed6f4f30 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6716f9d248190a145f6883827ebbe completed April 20, 2026, 6:33 p.m.
Created at: April 11, 2026, 11:40 p.m.