Triple
T13681793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of the Blessed Virgin Mary |
E328020
|
entity |
| Predicate | prayedAlongside |
P21327
|
FINISHED |
| Object | Divine Office |
—
|
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: Divine Office | Statement: [Office of the Blessed Virgin Mary, prayedAlongside, Divine Office]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prayedAlongside Context triple: [Office of the Blessed Virgin Mary, prayedAlongside, Divine Office]
-
A.
prayedDuring
Indicates that one entity performed prayer at some time within the duration of another specified event or time interval.
-
B.
praysAt
Indicates that one entity performs an act of prayer at, or directed toward, a specific place or site.
-
C.
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.
-
D.
praysTo
Indicates that one entity directs a prayer, supplication, or act of worship toward another entity as its spiritual or divine recipient.
-
E.
worshippedAlongside
Indicates that two deities or sacred figures were venerated together within the same religious context, ritual, or cult practice.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.