Triple
T34865575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VI Sunday of Easter |
E1004998
|
entity |
| Predicate | hasLiturgicalDayType |
P15353
|
FINISHED |
| Object | Sunday |
—
|
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: Sunday | Statement: [VI Sunday of Easter, hasLiturgicalDayType, Sunday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalDayType Context triple: [VI Sunday of Easter, hasLiturgicalDayType, Sunday]
-
A.
hasLiturgicalDay
chosen
Indicates that a particular date, event, or context is associated with a specific liturgical day within a religious calendar.
-
B.
hasLiturgicalPeriod
Indicates that something is associated with, occurs during, or is assigned to a specific liturgical period within a religious calendar.
-
C.
hasLiturgicalCategory
Indicates that something is classified under a particular liturgical category within a religious or worship-related system.
-
D.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
E.
liturgicalFeastType
Indicates the specific category or type of liturgical feast to which a given religious celebration or observance belongs.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4 p.m.