Triple
T34589881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visitation of the Blessed Virgin Mary |
E888148
|
entity |
| Predicate | dateChangeYear |
P91368
|
FINISHED |
| Object | 1969 |
—
|
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: 1969 | Statement: [Visitation of the Blessed Virgin Mary, dateChangeYear, 1969]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateChangeYear Context triple: [Visitation of the Blessed Virgin Mary, dateChangeYear, 1969]
-
A.
movedToCurrentDateYear
Indicates that an entity has been moved, updated, or adjusted so that its associated date now falls within the current calendar year.
-
B.
newYearDateGregorian
Indicates the specific calendar date on which New Year’s Day occurs according to the Gregorian calendar.
-
C.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
-
D.
eraChangeDate
Indicates the date on which one defined era or period ends and another begins.
-
E.
startDateInYear
chosen
Indicates that an entity’s start date occurs within a specified calendar year.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:03 a.m.