Triple
T4245699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Cross Cemetery (Culver City) |
E95522
|
entity |
| Predicate | hasBurialPlotType |
P6490
|
FINISHED |
| Object | ground burials |
—
|
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: ground burials | Statement: [Holy Cross Cemetery (Culver City), hasBurialPlotType, ground burials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialPlotType Context triple: [Holy Cross Cemetery (Culver City), hasBurialPlotType, ground burials]
-
A.
hasTypeOfBurial
chosen
Indicates the specific kind or method of burial associated with an entity.
-
B.
hasTypeOfGrave
Indicates that an entity is associated with a specific kind or category of grave.
-
C.
hasCemeteryType
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
-
D.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
E.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
- 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e8db5bc8190873c5ae3753aaa58 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.