Triple
T35692302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Philomena |
E1031326
|
entity |
| Predicate | liturgicalFeastSuppressedIn |
P183829
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Saint Philomena, liturgicalFeastSuppressedIn, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalFeastSuppressedIn Context triple: [Saint Philomena, liturgicalFeastSuppressedIn, 1961]
-
A.
liturgicalFeastDay
Indicates the date or occasion on which a religious figure, event, or mystery is formally commemorated in a liturgical calendar.
-
B.
liturgicalFeastType
Indicates the specific category or type of liturgical feast to which a given religious celebration or observance belongs.
-
C.
liturgicalCelebration
Indicates that one entity conducts or is associated with a formal act of worship or religious rite in honor of another entity, event, or sacred mystery.
-
D.
liturgicalCalendarFocus
Indicates the primary religious observance, theme, or commemoration that a liturgical calendar entry is centered on.
-
E.
liturgicalCalendarContext
Indicates the specific liturgical setting, season, or observance within which a religious action, text, or event takes place.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.