Triple
T15822833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral of Saint Joseph (Buffalo) |
E383654
|
entity |
| Predicate | hasMainAltarFor |
P119778
|
FINISHED |
| Object | diocesan liturgical celebrations |
—
|
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: diocesan liturgical celebrations | Statement: [Cathedral of Saint Joseph (Buffalo), hasMainAltarFor, diocesan liturgical celebrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAltarFor Context triple: [Cathedral of Saint Joseph (Buffalo), hasMainAltarFor, diocesan liturgical celebrations]
-
A.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
B.
hasAltarLocation
Indicates that an altar is situated at or associated with a specific location.
-
C.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
D.
hasAltarType
Indicates that an entity is associated with or characterized by a specific type or category of altar.
-
E.
hasAltarDedication
Indicates that an altar is dedicated to, in honor of, or in association with a particular entity or purpose.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a96b848190845cf547034a24f2 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.