Triple
T22423034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sollemnitas Domini Nostri Iesu Christi Universorum Regis |
E554295
|
entity |
| Predicate | celebrationFrequency |
P78772
|
FINISHED |
| Object | annual |
—
|
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: annual | Statement: [Sollemnitas Domini Nostri Iesu Christi Universorum Regis, celebrationFrequency, annual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celebrationFrequency Context triple: [Sollemnitas Domini Nostri Iesu Christi Universorum Regis, celebrationFrequency, annual]
-
A.
carnivalFrequency
Indicates how often a carnival event occurs within a given time period.
-
B.
awardedFrequency
Indicates how often an award or recognition is given within a specified time period.
-
C.
memorialEventFrequency
Indicates how often a memorial event occurs or is scheduled to take place.
-
D.
celebrationAssociatedWith
Indicates a relationship where a celebration is connected to, linked with, or held in relation to a particular entity, event, or context.
-
E.
hasFestivalFrequency
chosen
Indicates how often a festival or recurring celebratory event takes place within a given time period.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2af620819083338127e78137dc |
completed | April 29, 2026, 1:08 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:47 p.m.