Triple
T1019177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batak |
E22000
|
entity |
| Predicate | traditionalRitual |
P4193
|
FINISHED |
| Object | funerary ceremonies |
—
|
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: funerary ceremonies | Statement: [Batak, traditionalRitual, funerary ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRitual Context triple: [Batak, traditionalRitual, funerary ceremonies]
-
A.
ritualSpecialist
Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
-
B.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
-
C.
hasRitual
chosen
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
D.
traditionAscribes
Indicates that a tradition attributes or assigns a particular quality, role, origin, or action to an entity.
-
E.
notableRite
Indicates that an entity is associated with a significant or distinguished ritual, ceremony, or formal rite.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7c6005081909d9e56114c532d14 |
completed | March 1, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69a4b7238d4c8190b22d6c2ac0ac4911 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.