Triple
T4692557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Saints’ Day |
E104067
|
entity |
| Predicate | dayRelativeToEaster |
P58838
|
FINISHED |
| Object | fixed date feast |
—
|
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: fixed date feast | Statement: [All Saints’ Day, dayRelativeToEaster, fixed date feast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayRelativeToEaster Context triple: [All Saints’ Day, dayRelativeToEaster, fixed date feast]
-
A.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
B.
dateInEasternOrthodoxChurches
Indicates that the specified date is observed or used according to the liturgical calendar of Eastern Orthodox churches.
-
C.
dayOfMonth
Indicates the specific calendar day number within a given month on which something occurs or is associated.
-
D.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
E.
dateInAnglicanCommunion
Indicates that a given date is recognized and observed within the liturgical calendar of the Anglican Communion.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd660414b08190ab37467755d383b5 |
completed | March 20, 2026, 3:21 p.m. |
Created at: March 20, 2026, 1:16 p.m.