Triple
T11721538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prairie Home Cemetery |
E278643
|
entity |
| Predicate | hasBurialPurpose |
P25159
|
FINISHED |
| Object | public cemetery |
—
|
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: public cemetery | Statement: [Prairie Home Cemetery, hasBurialPurpose, public cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialPurpose Context triple: [Prairie Home Cemetery, hasBurialPurpose, public cemetery]
-
A.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
B.
usedForBurialOf
chosen
Indicates that something serves or is employed as a means, place, or object for burying a particular entity.
-
C.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
-
D.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c373088190bc2ae77a1696d280 |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.