Triple
T23567885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin Requiem Mass |
E580019
|
entity |
| Predicate | rubricalFeature |
P100245
|
FINISHED |
| Object | omission of the Gloria |
—
|
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: omission of the Gloria | Statement: [Latin Requiem Mass, rubricalFeature, omission of the Gloria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rubricalFeature Context triple: [Latin Requiem Mass, rubricalFeature, omission of the Gloria]
-
A.
rubricalSource
Indicates that one entity serves as the liturgical or rubrical source or authority from which the rules, instructions, or ceremonial guidelines for another entity are derived.
-
B.
rubricalInstruction
Indicates that one entity provides formal, rule-based guidance or directions governing how another entity should be performed, used, or interpreted.
-
C.
spanFeature
Indicates a relationship where a feature or characteristic extends across or covers a specified span or interval.
-
D.
featuresScoringSystem
Indicates that one entity incorporates or provides a particular scoring or rating system as part of its functionality or design.
-
E.
recognizedFeature
chosen
Indicates that a particular feature has been identified and acknowledged as present or valid in relation to an entity or 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6e11008190bdd28c3f85e3004e |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.