Triple
T2988577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Cross Cemetery, Colma, California, United States |
E80688
|
entity |
| Predicate | hasBurialTradition |
P4043
|
FINISHED |
| Object | Catholic burial rites |
—
|
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: Catholic burial rites | Statement: [Holy Cross Cemetery, Colma, California, United States, hasBurialTradition, Catholic burial rites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialTradition Context triple: [Holy Cross Cemetery, Colma, California, United States, hasBurialTradition, Catholic burial rites]
-
A.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
B.
burialPractice
chosen
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
C.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
D.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
E.
burialBy
Indicates that one entity is responsible for burying or interring 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c9cdd081908fa8094a3ac1f8d3 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.