Triple
T33082761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottawa Indians |
E846551
|
entity |
| Predicate | ceremonialSociety |
P69810
|
FINISHED |
| Object | Midewiwin |
—
|
NE NERFINISHED |
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: Midewiwin | Statement: [Ottawa Indians, ceremonialSociety, Midewiwin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialSociety Context triple: [Ottawa Indians, ceremonialSociety, Midewiwin]
-
A.
ceremonialAssociation
Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
-
B.
ceremonialSymbol
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
-
C.
initiationSociety
chosen
Indicates the relationship in which an entity is a member of, affiliated with, or participates in a society or group that conducts initiation rites or ceremonies.
-
D.
ceremonialLife
Indicates involvement in or association with formal rituals, traditions, or ceremonial practices within a social or cultural context.
-
E.
ceremonialOrigin
Indicates that something originates from, or is derived through, a formal ceremony or ritual practice.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:26 a.m.