Triple
T26529031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motet O magnum mysterium |
E670767
|
entity |
| Predicate | textLiturgicalFunction |
P10005
|
FINISHED |
| Object | responsory at Matins |
—
|
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: responsory at Matins | Statement: [Motet O magnum mysterium, textLiturgicalFunction, responsory at Matins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textLiturgicalFunction Context triple: [Motet O magnum mysterium, textLiturgicalFunction, responsory at Matins]
-
A.
liturgicalText
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
B.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical context.
-
C.
liturgicalCharacter
Indicates the specific role, function, or significance that something holds within a liturgical or worship context.
-
D.
liturgicalCelebration
Indicates that one entity conducts or is associated with a formal act of worship or religious rite in honor of another entity, event, or sacred mystery.
-
E.
liturgicalUsage
chosen
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:34 a.m.