Triple
T21406773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jayne Mansfield (cenotaph) |
E528055
|
entity |
| Predicate | cemeterySectionType |
P2742
|
FINISHED |
| Object | celebrity 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: celebrity cemetery | Statement: [Jayne Mansfield (cenotaph), cemeterySectionType, celebrity cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeterySectionType Context triple: [Jayne Mansfield (cenotaph), cemeterySectionType, celebrity cemetery]
-
A.
cemeterySection
Indicates that one entity is a specific section, area, or subdivision within a cemetery associated with the other entity.
-
B.
cemeteryType
chosen
Indicates the specific kind or classification of a cemetery associated with an entity.
-
C.
hasCemeteryType
Indicates that a cemetery is classified as belonging to a specific type or category of cemetery.
-
D.
cemeteryDivision
Indicates a subdivision or section within a cemetery that organizes or partitions the burial grounds.
-
E.
cemeteryStyle
Indicates the stylistic or design characteristics that define how a cemetery is arranged or presented.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b1b08fdc81909b3ba01add5f6484 |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:32 p.m.