Triple
T12106193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immaculate Heart of Mary |
E288308
|
entity |
| Predicate | worldConsecrationYear |
P31001
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Immaculate Heart of Mary, worldConsecrationYear, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldConsecrationYear Context triple: [Immaculate Heart of Mary, worldConsecrationYear, 1942]
-
A.
religiousEventYear
chosen
Indicates the calendar year in which a specified religious event took place or is scheduled to occur.
-
B.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
C.
pontificalYear
Indicates the specific year within a pope’s reign during which an event, document, or action took place.
-
D.
associatedSynodYear
Indicates the specific synod year with which an entity is associated or to which it pertains.
-
E.
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.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.