Triple
T14973069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bella Coola (Nuxalk) people |
E373371
|
entity |
| Predicate | ceremonialLife |
P116900
|
FINISHED |
| Object | potlatch ceremonies |
—
|
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: potlatch ceremonies | Statement: [Bella Coola (Nuxalk) people, ceremonialLife, potlatch ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialLife Context triple: [Bella Coola (Nuxalk) people, ceremonialLife, potlatch ceremonies]
-
A.
ceremonialFocus
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
-
B.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
C.
ceremonialOrigin
Indicates that something originates from, or is derived through, a formal ceremony or ritual practice.
-
D.
ceremonialCycle
Indicates a recurring sequence of rituals or formal events that are performed in a set order over a defined period.
-
E.
ceremonialSymbol
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
- F. None of above. chosen
Provenance (4 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e767608190940eb6f16ea97451 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:50 a.m.