Triple
T9793497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infant Mary |
E237660
|
entity |
| Predicate | hasDevotionalUse |
P59689
|
FINISHED |
| Object | private 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: private prayer | Statement: [Infant Mary, hasDevotionalUse, private prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDevotionalUse Context triple: [Infant Mary, hasDevotionalUse, private prayer]
-
A.
hasDevotionalFormula
Indicates a relationship where one entity includes, uses, or is associated with a specific devotional formula (such as a set religious phrase, prayer, or invocation).
-
B.
devotionalObject
chosen
Indicates that one entity is used by or associated with another as an object of religious or spiritual devotion.
-
C.
devotionalPracticesInclude
Indicates that certain devotional practices form a part or subset of a broader set of devotional activities associated with an entity.
-
D.
devotionalImportance
Indicates the degree to which something is regarded as significant or central within acts of devotion, worship, or religious practice.
-
E.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
- 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_69ca84dc04488190b9c91193976c0960 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda346945481908c2698a79c578ef5 |
completed | April 1, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:28 p.m.