Triple
T33124559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zurich municipal cemetery |
E847686
|
entity |
| Predicate | primaryBurialType |
P174147
|
FINISHED |
| Object | inhumation |
—
|
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: inhumation | Statement: [Zurich municipal cemetery, primaryBurialType, inhumation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBurialType Context triple: [Zurich municipal cemetery, primaryBurialType, inhumation]
-
A.
primaryDenominationOfBurials
Indicates the main religious denomination associated with the majority of burials at a given burial site or cemetery.
-
B.
burialPlotType
chosen
Indicates the specific kind or category of burial plot associated with an entity, such as its style, purpose, or usage designation.
-
C.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
firstBurial
Indicates that an entity is the earliest or initial burial associated with a person, place, or burial context.
-
E.
possiblyBurialOf
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.