Triple
T9842885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctus |
E239268
|
entity |
| Predicate | liturgicalTextType |
P17763
|
FINISHED |
| Object | acclamation |
—
|
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: acclamation | Statement: [Sanctus, liturgicalTextType, acclamation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalTextType Context triple: [Sanctus, liturgicalTextType, acclamation]
-
A.
liturgicalText
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
B.
liturgicalTextsFoundIn
Indicates that certain liturgical texts are located in, originate from, or are associated with a particular place or source.
-
C.
liturgicalGenre
chosen
Indicates the specific type or category of liturgical text, music, or ritual to which something belongs.
-
D.
liturgicalCalendarType
Indicates the specific type or system of liturgical calendar according to which religious feasts, seasons, and observances are organized.
-
E.
liturgicalFeastType
Indicates the specific category or type of liturgical feast to which a given religious celebration or observance belongs.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35c8e348190aa090c71bf6f30eb |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.