Triple
T9781910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angelus |
E237394
|
entity |
| Predicate | devotionalPosture |
P90627
|
FINISHED |
| Object | traditionally prayed kneeling |
—
|
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: traditionally prayed kneeling | Statement: [Angelus, devotionalPosture, traditionally prayed kneeling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: devotionalPosture Context triple: [Angelus, devotionalPosture, traditionally prayed kneeling]
-
A.
devotionalImportance
Indicates the degree to which something is regarded as significant or central within acts of devotion, worship, or religious practice.
-
B.
devotionalPracticesInclude
Indicates that certain devotional practices form a part or subset of a broader set of devotional activities associated with an entity.
-
C.
devotionalObject
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
D.
devotionalTitle
Indicates that one entity serves as the devotional or religiously themed title associated with another entity.
-
E.
communionPosture
Indicates the physical or bodily stance a person adopts while participating in communion.
- F. None of above. chosen
Provenance (4 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b23cb88190b458ab18d5f7f493 |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:27 p.m.