Triple

T12235460
Position Surface form Disambiguated ID Type / Status
Subject State Route 396 E291578 entity
Predicate isNumberedBefore P11124 FINISHED
Object State Route 397 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: State Route 397 | Statement: [State Route 396, isNumberedBefore, State Route 397]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: State Route 397
Context triple: [State Route 396, isNumberedBefore, State Route 397]
  • A. State Route 397 chosen
    State Route 397 is a state highway in Washington that serves as an important connector through the Tri-Cities area, linking industrial zones and major transportation routes in and around Benton County.
  • B. State Route 399
    State Route 399 is a Nevada state highway that serves as a local connector route within rural Pershing County.
  • C. State Route 39
    State Route 39 is a state highway in Ohio that serves as a key east–west route connecting several communities, including Dover.
  • D. State Route 39
    State Route 39 is a California state highway that runs from the Los Angeles Basin into the San Gabriel Mountains, providing key access to recreational areas in the Angeles National Forest.
  • E. State Route 396
    State Route 396 is a Nevada state highway that serves as a key local connector route within Pershing County.
  • 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_69d6ab668acc8190963ba424049d6aee completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d91cb2892c81909a97b3ad6ec2c21b completed April 10, 2026, 3:52 p.m.
Created at: April 8, 2026, 9:51 p.m.