Triple
T14345754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oto people |
E355713
|
entity |
| Predicate | sharedCultureWith |
P33545
|
FINISHED |
| Object | other Siouan-speaking tribes |
—
|
LITERAL 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: other Siouan-speaking tribes | Statement: [Oto people, sharedCultureWith, other Siouan-speaking tribes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedCultureWith Context triple: [Oto people, sharedCultureWith, other Siouan-speaking tribes]
-
A.
sharesCultWith
Indicates that two entities belong to or participate in the same cult or cult-like religious group.
-
B.
shareCultureWith
chosen
Indicates that two entities mutually participate in, express, or are influenced by the same cultural practices, values, or traditions.
-
C.
sharesTraditionsWith
Indicates that two entities have customs, practices, or cultural traditions in common or mutually observe similar traditional activities.
-
D.
sharesLanguageWith
Indicates that two entities use at least one common language for communication.
-
E.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
- F. None of above.
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. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.