Triple
T23807068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misereatur prayer |
E589736
|
entity |
| Predicate | liturgicalSpeakerRole |
P11534
|
FINISHED |
| Object | celebrant |
—
|
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: celebrant | Statement: [Misereatur prayer, liturgicalSpeakerRole, celebrant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalSpeakerRole Context triple: [Misereatur prayer, liturgicalSpeakerRole, celebrant]
-
A.
liturgicalRole
chosen
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
B.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
C.
ecclesialRole
Indicates that one entity holds or is assigned a specific role, office, or function within a church or ecclesiastical structure in relation to another entity.
-
D.
liturgicalCharacter
Indicates the specific role, function, or significance that something holds within a liturgical or worship context.
-
E.
theologicalRole
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c752ff6481908cfc20d4f178d526 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.