Triple
T34896977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter Week VII in the Roman Rite |
E1006461
|
entity |
| Predicate | hasAlleluia |
P195011
|
FINISHED |
| Object | retained in Mass and Liturgy of the Hours |
—
|
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: retained in Mass and Liturgy of the Hours | Statement: [Easter Week VII in the Roman Rite, hasAlleluia, retained in Mass and Liturgy of the Hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlleluia Context triple: [Easter Week VII in the Roman Rite, hasAlleluia, retained in Mass and Liturgy of the Hours]
-
A.
hasAgnusDei
Indicates that one entity possesses or includes an Agnus Dei (a representation or object symbolizing the Lamb of God).
-
B.
hasCanticle
Indicates that an entity is associated with, contains, or is characterized by a specific canticle (a hymn or song of praise).
-
C.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
-
D.
hasChorusIn
Indicates that a musical work includes a chorus section within the specified part or segment.
-
E.
hasChorus
Indicates that something (typically a song or musical piece) includes a chorus section as part of its structure.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 3, 2026, 4 p.m.