Triple
T11154928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Syrian Anaphora of Saint Basil |
E263881
|
entity |
| Predicate | principalPrayerType |
P21327
|
FINISHED |
| Object | Eucharistic prayer |
—
|
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: Eucharistic prayer | Statement: [West Syrian Anaphora of Saint Basil, principalPrayerType, Eucharistic prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalPrayerType Context triple: [West Syrian Anaphora of Saint Basil, principalPrayerType, Eucharistic prayer]
-
A.
prayerForm
Indicates the specific manner, style, or structure in which a prayer is expressed or performed.
-
B.
associatedPrayer
chosen
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
C.
prayerCall
Indicates that one entity issues or performs a call to prayer directed toward others.
-
D.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
E.
principalSacrament
Indicates that one sacrament holds primary or highest importance in relation to another or within a given religious or ritual 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8741cd48190b7cc29c6b6bc54ff |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce71944819089eee9b5c9283cbd |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.