Triple
T32316222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caeremoniale Episcoporum (1600) |
E825638
|
entity |
| Predicate | liturgicalLevel |
P173962
|
FINISHED |
| Object | pontifical |
—
|
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: pontifical | Statement: [Caeremoniale Episcoporum (1600), liturgicalLevel, pontifical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalLevel Context triple: [Caeremoniale Episcoporum (1600), liturgicalLevel, pontifical]
-
A.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
B.
liturgicalMood
Indicates the characteristic emotional or spiritual tone associated with a liturgical practice, rite, or season.
-
C.
liturgicalFormIncludes
Indicates that one liturgical form contains, incorporates, or makes use of another liturgical element or structure.
-
D.
hasLiturgicalNature
Indicates that something possesses a liturgical character or function, typically relating to formal religious worship or rites.
-
E.
liturgicalStyle
Indicates the manner or form of worship practice or ritual expression associated with a religious service or tradition.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdbb00d4819083dd799d7d417f20 |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:46 a.m.