Triple

T15053932
Position Surface form Disambiguated ID Type / Status
Subject Sweet Home, Oregon E379437 entity
Predicate locatedOnHighway P385 FINISHED
Object Oregon Route 228 E830546 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 228 | Statement: [Sweet Home, Oregon, locatedOnHighway, Oregon Route 228]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Oregon Route 228
Context triple: [Sweet Home, Oregon, locatedOnHighway, Oregon Route 228]
  • A. Oregon Route 228 chosen
    Oregon Route 228 is a state highway in Oregon that connects the communities of Halsey and Sweet Home, running through rural Linn County.
  • B. Oregon Route 221
    Oregon Route 221 is a state highway in Oregon that runs along the Willamette River, connecting the Salem area with communities such as Dayton.
  • C. 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.
  • D. Oregon Route 22
    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.
  • E. Oregon Route 227
    Oregon Route 227 is a state highway in Oregon that connects the city of Canyonville with communities to the east through the forested terrain of southwestern Oregon.
  • 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_69d85cd64d108190853797a95c11cc45 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69deda92091c81909180f486edf01405 completed April 15, 2026, 12:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69febfdc8f64819083c7e3510e671b9a completed May 9, 2026, 5:02 a.m.
Created at: April 10, 2026, 3:01 a.m.