Triple
T22032184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsou people |
E544111
|
entity |
| Predicate | ceremonialCulture |
P116900
|
FINISHED |
| Object | rich ceremonial traditions |
—
|
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: rich ceremonial traditions | Statement: [Tsou people, ceremonialCulture, rich ceremonial traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialCulture Context triple: [Tsou people, ceremonialCulture, rich ceremonial traditions]
-
A.
ceremonialLife
chosen
Indicates involvement in or association with formal rituals, traditions, or ceremonial practices within a social or cultural context.
-
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.
ceremonialFocus
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
-
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.
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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ee84848190a22c24bf14498520 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.