Triple
T1209714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solemnity of the Most Holy Body and Blood of Christ |
E25969
|
entity |
| Predicate | isHolyDayOfObligationIn |
P13859
|
FINISHED |
| Object | some countries |
—
|
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: some countries | Statement: [Solemnity of the Most Holy Body and Blood of Christ, isHolyDayOfObligationIn, some countries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHolyDayOfObligationIn Context triple: [Solemnity of the Most Holy Body and Blood of Christ, isHolyDayOfObligationIn, some countries]
-
A.
holyDayOfObligationIn
chosen
Indicates that a particular day is recognized as a holy day of obligation within a specified religious jurisdiction or region.
-
B.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
-
C.
isFederalHoliday
Indicates that a given day is officially recognized as a federal holiday by the national government.
-
D.
isWorkHoliday
Indicates that a given day is designated as a non-working public or company holiday.
-
E.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bde30ce08190ab60a181ad2d321d |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.