Triple
T20313619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Saturday |
E510320
|
entity |
| Predicate | positionInTriduum |
P15827
|
FINISHED |
| Object | second day of the Easter Triduum |
—
|
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: second day of the Easter Triduum | Statement: [Easter Saturday, positionInTriduum, second day of the Easter Triduum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTriduum Context triple: [Easter Saturday, positionInTriduum, second day of the Easter Triduum]
-
A.
positionInHolyWeek
chosen
Indicates the specific place or order that a day, event, or observance occupies within the sequence of days in Holy Week.
-
B.
positionOnRitual
Indicates the stance, role, or placement an entity holds with respect to a particular ritual or ceremonial practice.
-
C.
positionOnTrident
Indicates that one entity occupies a specific location or slot on a trident-like structure or configuration.
-
D.
positionInUnderworld
Indicates a hierarchical or role-based position that an entity holds within an underworld or criminal organization.
-
E.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67745e2448190b5611382fe338bb2 |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.