Triple
T4767833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visitation |
E105854
|
entity |
| Predicate | AnglicanDate |
P7862
|
FINISHED |
| Object | May 31 |
—
|
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: May 31 | Statement: [Visitation, AnglicanDate, May 31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AnglicanDate Context triple: [Visitation, AnglicanDate, May 31]
-
A.
dateInAnglicanCommunion
chosen
Indicates that a given date is recognized and observed within the liturgical calendar of the Anglican Communion.
-
B.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
C.
dateInRomanCatholicChurch
Indicates that a specific date is recognized, observed, or used within the context of the Roman Catholic Church’s liturgical or ecclesiastical calendar.
-
D.
dateInEasternOrthodoxChurches
Indicates that the specified date is observed or used according to the liturgical calendar of Eastern Orthodox churches.
-
E.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.