Triple
T2564133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian saints |
E57309
|
entity |
| Predicate | hasFeastDays |
P9516
|
FINISHED |
| Object | liturgical feast days |
—
|
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: liturgical feast days | Statement: [Christian saints, hasFeastDays, liturgical feast days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFeastDays Context triple: [Christian saints, hasFeastDays, liturgical feast days]
-
A.
hasAssociatedFeast
chosen
Indicates that something (such as a person, event, or entity) is linked to a specific feast or celebratory religious observance.
-
B.
isMovableFeast
Indicates that an event or celebration occurs on a date that changes from year to year rather than being fixed on the calendar.
-
C.
containsFixedFeasts
Indicates that an entity includes or encompasses specific feasts that occur on fixed, recurring calendar dates.
-
D.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
E.
containsMovableFeasts
Indicates that a time period, calendar, or schedule includes events or observances whose dates change from year to year.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35c6ee88190b6eaa1841d3e99a4 |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.