Triple
T9494934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Santiago de Compostela |
E228979
|
entity |
| Predicate | holyYearCondition |
P88935
|
FINISHED |
| Object | when 25 July falls on a Sunday |
—
|
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: when 25 July falls on a Sunday | Statement: [Archdiocese of Santiago de Compostela, holyYearCondition, when 25 July falls on a Sunday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holyYearCondition Context triple: [Archdiocese of Santiago de Compostela, holyYearCondition, when 25 July falls on a Sunday]
-
A.
religiousEventYear
Indicates the calendar year in which a specified religious event took place or is scheduled to occur.
-
B.
hasOverrulingYear
Indicates the year in which a prior decision, rule, or action was formally overruled or invalidated.
-
C.
hasTypeOfYear
Indicates that a given year is classified as belonging to a specific type or category of year (e.g., fiscal, academic, leap).
-
D.
yearPassed
Indicates that a specified number of calendar years has elapsed between two time points or events.
-
E.
assumedRuleYear
Indicates the year in which a particular rule, regulation, or policy is assumed to take effect or be applicable.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95ea4a04819092c7842361c6296e |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca8c6b0f081908334d6c7cf80e03c |
completed | April 1, 2026, 5:10 a.m. |
Created at: March 30, 2026, 7:56 p.m.