Triple
T2819199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Fifty Days |
E54365
|
entity |
| Predicate | liturgicalYearPart |
P27466
|
FINISHED |
| Object | Easter cycle |
—
|
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: Easter cycle | Statement: [Great Fifty Days, liturgicalYearPart, Easter cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalYearPart Context triple: [Great Fifty Days, liturgicalYearPart, Easter cycle]
-
A.
liturgicalSeasonContext
Indicates the specific liturgical season within which a religious action, event, or text takes place or is understood.
-
B.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
C.
hasLiturgicalPeriod
chosen
Indicates that something is associated with, occurs during, or is assigned to a specific liturgical period within a religious calendar.
-
D.
usesLiturgicalCalendar
Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
-
E.
liturgicalSeasonVariation
Indicates that something changes or differs depending on the liturgical season within a religious calendar or worship cycle.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abdf15b7288190a03d1193cc0544a6 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd08f2f481908c3da8a9c7a00552 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.