Triple
T16725267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panteón de Dolores |
E406448
|
entity |
| Predicate | burialCustomsObserved |
P74935
|
FINISHED |
| Object | Day of the Dead visits |
—
|
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: Day of the Dead visits | Statement: [Panteón de Dolores, burialCustomsObserved, Day of the Dead visits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialCustomsObserved Context triple: [Panteón de Dolores, burialCustomsObserved, Day of the Dead visits]
-
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.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
C.
burialCulture
Indicates the cultural practices, norms, or traditions associated with how a person or remains are buried.
-
D.
hasPrimaryReligionOfBurials
Indicates that a group or community predominantly practices a particular religion in the context of its burial customs or rites.
-
E.
burialPolicy
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38746c8fc81908b9fade26f37be11 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.