Triple
T37101399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burial Hill cemetery |
E918711
|
entity |
| Predicate | hasGravestoneArt |
P11281
|
FINISHED |
| Object | death’s head motifs |
—
|
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: death’s head motifs | Statement: [Burial Hill cemetery, hasGravestoneArt, death’s head motifs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGravestoneArt Context triple: [Burial Hill cemetery, hasGravestoneArt, death’s head motifs]
-
A.
hasGravestone
Indicates that one entity possesses, is associated with, or is commemorated by a gravestone.
-
B.
hasGraveInscription
Indicates that an entity (typically a grave or tomb) bears a specific inscription engraved or written on it.
-
C.
hasGravestoneStyle
chosen
Indicates that an entity’s gravestone is characterized by or associated with a particular style or design.
-
D.
hasGraveOrMemorialOf
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
E.
hasGraveMarkerShape
Indicates that one entity (a grave or burial site) has a grave marker whose physical form or outline matches the specified shape.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:14 p.m.