Triple
T23433426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakota Sioux |
E563392
|
entity |
| Predicate | usesClanTotems |
P116140
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nakota Sioux, usesClanTotems, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClanTotems Context triple: [Nakota Sioux, usesClanTotems, true]
-
A.
hasClanSymbol
Indicates that an entity is associated with a particular clan through a specific identifying symbol.
-
B.
clanCrestAssociatedWith
Indicates that a particular clan crest is symbolically or traditionally linked to a specific clan or family.
-
C.
hasTotem
chosen
Indicates that one entity possesses, is symbolically represented by, or is associated with another entity as its totem.
-
D.
usesClanPraise
Indicates that one entity employs or invokes the traditional praise names or laudatory expressions associated with a particular clan in relation to another entity.
-
E.
hasClanBadgePlant
Indicates that an entity’s clan badge features or includes a specific plant as part of its design.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5d9f0d48190903f43d044bcf2dd |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:49 p.m.