Triple
T35859773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalumpang Toraja |
E1036912
|
entity |
| Predicate | hasFuneraryTraditions |
P74935
|
FINISHED |
| Object | Toraja funerary rites |
—
|
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: Toraja funerary rites | Statement: [Kalumpang Toraja, hasFuneraryTraditions, Toraja funerary rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFuneraryTraditions Context triple: [Kalumpang Toraja, hasFuneraryTraditions, Toraja funerary rites]
-
A.
hasBurialCustoms
chosen
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
B.
funeraryBelief
Indicates a belief or doctrine concerning death, the afterlife, or practices and meanings associated with funerary rites.
-
C.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
D.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
E.
hasBurialPlaceTradition
Indicates a relationship where a person or group is associated with a traditional or customary place of burial.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.