Triple
T13272470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toraja people |
E316098
|
entity |
| Predicate | ritualAnimal |
P11837
|
FINISHED |
| Object | water buffalo |
—
|
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: water buffalo | Statement: [Toraja people, ritualAnimal, water buffalo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ritualAnimal Context triple: [Toraja people, ritualAnimal, water buffalo]
-
A.
sacrificedAnimalsAt
Indicates that an entity performed or conducted animal sacrifices at a specific location or site.
-
B.
sacrificeAnimalType
chosen
Indicates that an entity performs or is involved in the act of sacrificing an animal of a specified type.
-
C.
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.
-
D.
ritualCategory
Indicates the classification relationship that assigns a ritual to a specific ritual type or category.
-
E.
ritualEvent
Indicates that an event is a ritual or ceremonial occurrence, typically involving prescribed actions, symbols, or practices performed according to tradition or custom.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.