Triple
T439945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacré-Cœur Basilica |
E10091
|
entity |
| Predicate | consecratedIn |
P3356
|
FINISHED |
| Object | 1919 |
—
|
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: 1919 | Statement: [Sacré-Cœur Basilica, consecratedIn, 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consecratedIn Context triple: [Sacré-Cœur Basilica, consecratedIn, 1919]
-
A.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
B.
presanctifiedGiftsConsecratedAt
Indicates that the presanctified gifts were consecrated at a particular time, place, or liturgical celebration.
-
C.
consecrationDate
chosen
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
D.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
E.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2977888190a0590b2c1bd2f5da |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.