Triple
T17847543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinook tribe |
E445702
|
entity |
| Predicate | spiritualSpecialist |
P17182
|
FINISHED |
| Object | shamans |
—
|
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: shamans | Statement: [Chinook tribe, spiritualSpecialist, shamans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spiritualSpecialist Context triple: [Chinook tribe, spiritualSpecialist, shamans]
-
A.
spiritualityType
Indicates the specific kind or category of spirituality associated with an entity.
-
B.
spiritualDirector
Indicates a relationship where one entity serves as a spiritual guide, mentor, or counselor to another in matters of faith and personal spiritual growth.
-
C.
spiritualMeans
Indicates that one entity serves as a spiritual method, medium, or pathway through which another entity attains or engages in a spiritual state, goal, or practice.
-
D.
ritualSpecialist
chosen
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
E.
spiritualQuest
Indicates a process in which an entity actively seeks deeper spiritual understanding, growth, or enlightenment.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffc5fec8190adc66f7b0e264d5f |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.