Triple
T38289463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John |
E1022317
|
entity |
| Predicate | feastDayInLutheranChurches |
P86735
|
FINISHED |
| Object | 27 December |
—
|
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: 27 December | Statement: [St John, feastDayInLutheranChurches, 27 December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feastDayInLutheranChurches Context triple: [St John, feastDayInLutheranChurches, 27 December]
-
A.
LutheranDate
Indicates that a given date is observed or calculated according to the Lutheran liturgical or ecclesiastical calendar.
-
B.
liturgicalFeastDay
chosen
Indicates the date or occasion on which a religious figure, event, or mystery is formally commemorated in a liturgical calendar.
-
C.
feastDayObservedOn
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
D.
institutedFeast
Indicates that an authority or group formally established and put into practice a particular feast or festival as an ongoing observance.
-
E.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.