Triple

T7369703
Position Surface form Disambiguated ID Type / Status
Subject Washington State Route 18 E169964 entity
Predicate abbreviation P43 FINISHED
Object SR 18 E52511 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: SR 18 | Statement: [Washington State Route 18, abbreviation, SR 18]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SR 18
Context triple: [Washington State Route 18, abbreviation, SR 18]
  • A. SR 18 chosen
    SR 18 is a state highway in Georgia that runs east–west across the central part of the state, connecting several small towns and regional routes.
  • B. SR 188
    SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
  • C. SR 180
    SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
  • D. SR 16
    SR 16 is a state highway in Georgia that runs east–west across the central part of the state, connecting several towns and major routes.
  • E. SR 168
    SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
  • 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_69c68a5ade988190885b7175f63b7534 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f1810668819094aec4b237d08068 completed March 27, 2026, 9:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802c3a4788190850294b054b9c928 completed March 28, 2026, 4:33 p.m.
Created at: March 27, 2026, 3:07 p.m.