Triple
T2363039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian liturgical year |
E47316
|
entity |
| Predicate | containsFixedFeasts |
P38234
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Christian liturgical year, containsFixedFeasts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFixedFeasts Context triple: [Christian liturgical year, containsFixedFeasts, true]
-
A.
isFixedFeast
Indicates that an event or celebration occurs on the same calendar date every year, rather than moving relative to other dates.
-
B.
definesFeastDate
Indicates that one entity specifies or determines the calendar date on which a particular feast or festival is observed.
-
C.
hasAssociatedFeast
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
D.
isMovableFeast
Indicates that an event or celebration occurs on a date that changes from year to year rather than being fixed on the calendar.
-
E.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
- F. None of above. chosen
Provenance (4 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc74501388190adce9b3e51a03ded |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc6a85e2c8190afec217ff29476be |
completed | March 7, 2026, 6:33 a.m. |
Created at: March 4, 2026, 7:55 p.m.