Triple
T35571647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westlawn Cemetery, Norridge, Illinois |
E1027954
|
entity |
| Predicate | followsBurialTradition |
P74935
|
FINISHED |
| Object | Jewish burial customs |
—
|
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 customs | Statement: [Westlawn Cemetery, Norridge, Illinois, followsBurialTradition, Jewish burial customs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsBurialTradition Context triple: [Westlawn Cemetery, Norridge, Illinois, followsBurialTradition, Jewish burial customs]
-
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.
hasBurialPlaceTradition
Indicates a relationship where a person or group is associated with a traditional or customary place of burial.
-
D.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
E.
followsRitualTraditionOf
Indicates that one entity practices, observes, or adheres to the ritual traditions established or maintained by another entity.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 3, 2026, 4:04 p.m.