Triple
T20335532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King David Memorial Park |
E492596
|
entity |
| Predicate | followsBurialCustom |
P74935
|
FINISHED |
| Object | Jewish burial traditions |
—
|
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: Jewish burial traditions | Statement: [King David Memorial Park, followsBurialCustom, Jewish burial traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsBurialCustom Context triple: [King David Memorial Park, followsBurialCustom, Jewish burial traditions]
-
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.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
burialPolicy
Indicates the rules or arrangements governing how and under what conditions a person’s body is to be buried.
-
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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677eb4d5881908ea5ec5a1dd7eafa |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:23 a.m.