Triple
T19888966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pelinna |
E477977
|
entity |
| Predicate | funeraryBelief |
P137714
|
FINISHED |
| Object | afterlife guidance texts on gold tablets |
—
|
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: afterlife guidance texts on gold tablets | Statement: [Pelinna, funeraryBelief, afterlife guidance texts on gold tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funeraryBelief Context triple: [Pelinna, funeraryBelief, afterlife guidance texts on gold tablets]
-
A.
burialCulture
Indicates the cultural practices, norms, or traditions associated with how a person or remains are buried.
-
B.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
C.
hasPrimaryReligionOfBurials
Indicates that a group or community predominantly practices a particular religion in the context of its burial customs or rites.
-
D.
burials
Indicates that one entity is interred or laid to rest in a grave or burial site associated with another entity.
-
E.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
- F. None of above. chosen
Provenance (4 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590c1b9c8190abbfaa04b80713b3 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.