Triple
T13502639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huautla de Jiménez region |
E320930
|
entity |
| Predicate | healingRitualName |
P48495
|
FINISHED |
| Object | velada |
—
|
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: velada | Statement: [Huautla de Jiménez region, healingRitualName, velada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: healingRitualName Context triple: [Huautla de Jiménez region, healingRitualName, velada]
-
A.
hasRitualName
Indicates that an entity is associated with a specific name used in a ritual or ceremonial context.
-
B.
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.
-
C.
ritualTitle
chosen
Indicates the formal name or designation assigned to a specific ritual within a cultural, religious, or ceremonial context.
-
D.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
E.
ritualOutcome
Indicates the result or consequence produced by performing a particular ritual.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf50f4a48190a44fc537b78c32fd |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.