Triple
T11274119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother most pure |
E266886
|
entity |
| Predicate | roleInPrayer |
P27714
|
FINISHED |
| Object | invocation seeking purity |
—
|
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: invocation seeking purity | Statement: [Mother most pure, roleInPrayer, invocation seeking purity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPrayer Context triple: [Mother most pure, roleInPrayer, invocation seeking purity]
-
A.
statusInPrayer
Indicates the specific role, posture, or condition an entity holds while engaged in a prayer activity.
-
B.
positionInPrayer
Indicates the specific posture or stage a participant occupies within the sequence of actions in a prayer.
-
C.
positionOnPrayer
Indicates a stance, view, or policy that an entity holds regarding the practice or role of prayer.
-
D.
roleInRitual
chosen
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
E.
liturgicalRole
Indicates the specific function or position an entity holds within a religious or liturgical 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e965c9048190804ebb48f0a4817b |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.