Triple
T14345750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oto people |
E355713
|
entity |
| Predicate | endonym |
P1435
|
FINISHED |
| Object | Otoe |
E348922
|
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: Otoe | Statement: [Oto people, endonym, Otoe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Otoe Context triple: [Oto people, endonym, Otoe]
-
A.
Otoe
chosen
The Otoe are a Native American tribe of the Siouan language family historically located along the Missouri River in the central United States.
-
B.
Osage River
The Osage River is a major river in central Missouri known for its role in regional hydroelectric power generation and recreation, including the creation of the Lake of the Ozarks.
-
C.
Kans River
Kans River is a regional river flowing through Rajasthan in northwestern India, including the Bundi district.
-
D.
Pawnee River
The Pawnee River is a tributary of the Arkansas River in western Kansas, flowing through the High Plains and supporting local agriculture and wildlife habitats.
-
E.
Nodaway River
The Nodaway River is a tributary of the Missouri River flowing through parts of Iowa and Missouri, historically significant enough to lend its name to Nodaway 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8b81bc8190ace2a575faf55cc0 |
completed | April 14, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda907abf88190b86ce65390d9ca40 |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 10, 2026, 1:14 a.m.