Triple
T31944865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Requiem et Kyrie |
E815622
|
entity |
| Predicate | precededByInLiturgy |
P24046
|
FINISHED |
| Object | Introductory rites of the Mass |
—
|
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: Introductory rites of the Mass | Statement: [Requiem et Kyrie, precededByInLiturgy, Introductory rites of the Mass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByInLiturgy Context triple: [Requiem et Kyrie, precededByInLiturgy, Introductory rites of the Mass]
-
A.
pairedWithInLiturgy
Indicates that two entities are customarily used or referenced together within a liturgical context or ceremony.
-
B.
usedInLiturgy
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
C.
consecratedInPresenceOf
Indicates that the act of consecration was performed while a specified person, group, or entity was present as a witness or participant.
-
D.
liturgicalSequence
chosen
Indicates the ordered progression of rites, prayers, or ceremonies within a liturgical service.
-
E.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 12:06 a.m.