Triple
T697251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsis |
E13919
|
entity |
| Predicate | funeraryCustom |
P4043
|
FINISHED |
| Object | sky burial on Towers of Silence |
—
|
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: sky burial on Towers of Silence | Statement: [Parsis, funeraryCustom, sky burial on Towers of Silence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: funeraryCustom Context triple: [Parsis, funeraryCustom, sky burial on Towers of Silence]
-
A.
burialPractice
chosen
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
B.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
C.
hasLifecycleRitual
Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
-
D.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
E.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.