Triple
T2567707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Dance |
E57389
|
entity |
| Predicate | hasSacredObject |
P7123
|
FINISHED |
| Object | central cottonwood pole |
—
|
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: central cottonwood pole | Statement: [Sun Dance, hasSacredObject, central cottonwood pole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredObject Context triple: [Sun Dance, hasSacredObject, central cottonwood pole]
-
A.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
B.
hasRitualObject
chosen
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
E.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd36191848190b6255fa9029429bd |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.