Triple
T17793329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serawai people |
E444222
|
entity |
| Predicate | funeraryCustoms |
P74935
|
FINISHED |
| Object | Islamic burial practices with local adat elements |
—
|
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: Islamic burial practices with local adat elements | Statement: [Serawai people, funeraryCustoms, Islamic burial practices with local adat elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funeraryCustoms Context triple: [Serawai people, funeraryCustoms, Islamic burial practices with local adat elements]
-
A.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
B.
burialCulture
Indicates the cultural practices, norms, or traditions associated with how a person or remains are buried.
-
C.
hasBurialCustoms
chosen
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
D.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
E.
mourningCustom
Indicates a culturally prescribed way in which people are expected to express grief and honor the dead after a loss.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487993a6c8190805e06d93dfc0dce |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.