Triple
T32245312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Heights Cemetery |
E823729
|
entity |
| Predicate | burialPlotType |
P174147
|
FINISHED |
| Object | family plots |
—
|
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: family plots | Statement: [Western Heights Cemetery, burialPlotType, family plots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialPlotType Context triple: [Western Heights Cemetery, burialPlotType, family plots]
-
A.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
B.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
C.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
D.
burialPlotMarkedBy
Indicates that a burial plot is identified or distinguished by a particular marker, such as a headstone, plaque, or other physical sign.
-
E.
burialPlotGuardedBy
Indicates that a burial plot is protected or watched over by a specified guardian or guarding entity.
- F. None of above. chosen
Provenance (4 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:40 a.m.