Triple
T10180718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Route 7 |
E236773
|
entity |
| Predicate | crossesRiver |
P416
|
FINISHED |
| Object | Burnt River |
E425362
|
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: Burnt River | Statement: [Oregon Route 7, crossesRiver, Burnt River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Burnt River Context triple: [Oregon Route 7, crossesRiver, Burnt River]
-
A.
Burnt River
chosen
Burnt River is a river in eastern Oregon that flows through rugged canyon country before joining the Snake River.
-
B.
Magothy River
The Magothy River is a tidal sub-estuary of the Chesapeake Bay in Maryland, known for its recreational boating, waterfront communities, and ecological significance.
-
C.
River Hindburn
The River Hindburn is a small river in Lancashire, England, that flows through rural valleys and villages before joining the River Lune.
-
D.
Roaring River
Roaring River is a tributary stream in North Carolina that feeds into the Yadkin River and is known for its scenic, fast-flowing waters.
-
E.
Roaring River
Roaring River is a mountain river known for flowing through the rugged terrain of Cloud Canyon, likely featuring swift currents and scenic cascades.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded315f14819085727bd9b4363d10 |
completed | April 2, 2026, 4:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76b9112948190a0dd747a67f8206a |
completed | May 3, 2026, 3:36 p.m. |
Created at: March 30, 2026, 9:11 p.m.