Triple
T12240489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellefontaine Cemetery |
E291714
|
entity |
| Predicate | BuschMausoleumStyle |
P103971
|
FINISHED |
| Object | Romanesque Revival |
—
|
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: Romanesque Revival | Statement: [Bellefontaine Cemetery, BuschMausoleumStyle, Romanesque Revival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BuschMausoleumStyle Context triple: [Bellefontaine Cemetery, BuschMausoleumStyle, Romanesque Revival]
-
A.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
B.
cemeteryStyle
Indicates the stylistic or design characteristics that define how a cemetery is arranged or presented.
-
C.
hasPartInMausoleum
Indicates that an entity is a component, section, or element contained within or forming part of a mausoleum.
-
D.
majorMortuaryComplex
Indicates a significant funerary or burial-related architectural complex that serves as a primary site for mortuary activities.
-
E.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d92468052c819090546f36d009a64f |
completed | April 10, 2026, 4:25 p.m. |
Created at: April 8, 2026, 9:51 p.m.