Triple
T31588979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatung |
E806036
|
entity |
| Predicate | ritualTechnique |
P4193
|
FINISHED |
| Object | entering trance state |
—
|
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: entering trance state | Statement: [Tatung, ritualTechnique, entering trance state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualTechnique Context triple: [Tatung, ritualTechnique, entering trance state]
-
A.
ritualSpecialization
Indicates a relationship where an entity is specifically focused on, trained in, or primarily responsible for performing a particular type of ritual or set of ritual practices.
-
B.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
ritualTechnology
Indicates a relationship where a technology is used, shaped, or defined by ritual practices or ceremonial procedures.
-
D.
ritualTreatment
Indicates a relationship where an entity performs or undergoes a ritualized act or procedure intended to affect, purify, protect, or transform another entity or condition.
-
E.
hasRitualSystem
Indicates that an entity possesses or is associated with a structured set of rituals or ceremonial practices.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a82eb2848190b5329618001a90fd |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:27 p.m.