Triple

T13321078
Position Surface form Disambiguated ID Type / Status
Subject Detroit, Oregon E317314 entity
Predicate locatedOn P40 FINISHED
Object Oregon Route 22 E174984 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: Oregon Route 22 | Statement: [Detroit, Oregon, locatedOn, Oregon Route 22]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Oregon Route 22
Context triple: [Detroit, Oregon, locatedOn, Oregon Route 22]
  • A. Oregon Route 22 chosen
    Oregon Route 22 is a primary east–west state highway in Oregon that connects the Willamette Valley, including Salem, to the central Oregon coast and the Cascade Range.
  • B. Oregon Route 202
    Oregon Route 202 is a state highway in northwestern Oregon that runs between Astoria and Jewell through forested and coastal areas.
  • C. Oregon Route 20
    Oregon Route 20 is a major east–west state highway in Oregon that runs from the central coast through the Willamette Valley and across the Cascades into eastern Oregon.
  • D. Oregon Route 203
    Oregon Route 203 is a state highway in northeastern Oregon that connects rural communities and scenic areas in and around Union County.
  • E. Oregon Route 228
    Oregon Route 228 is a state highway in Oregon that connects the communities of Halsey and Sweet Home, running through rural Linn County.
  • 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_69d806b4d62c81908d4ced1665414be5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9992ab83c8190982d9f54dff6919f completed April 11, 2026, 12:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69f77f7a13508190bbab6eb68fb52a18 completed May 3, 2026, 5:01 p.m.
Created at: April 9, 2026, 9:30 p.m.