Triple
T24026931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Corpus Christi |
E594988
|
entity |
| Predicate | includesPrayerType |
P37362
|
FINISHED |
| Object | Vespers |
—
|
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: Vespers | Statement: [Office of Corpus Christi, includesPrayerType, Vespers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesPrayerType Context triple: [Office of Corpus Christi, includesPrayerType, Vespers]
-
A.
containsPrayerType
chosen
Indicates that one entity includes or encompasses a specific type or category of prayer.
-
B.
hasPrayerRite
Indicates that one entity is associated with, follows, or practices a particular prayer rite or liturgical form.
-
C.
associatedPrayer
Indicates a relationship where a specific prayer is linked or connected to another entity, such as an event, object, person, or religious context.
-
D.
praysIn
Indicates that an entity performs the act of praying within or at a particular place or setting.
-
E.
canBePrayed
Indicates that an entity is a suitable or valid target for prayer or religious supplication.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76c083c819090784ecb42effbae |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.