Triple
T4070915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assumption of Mary |
E86642
|
entity |
| Predicate | hasTheologicalType |
P5493
|
FINISHED |
| Object | glorification of Mary |
—
|
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: glorification of Mary | Statement: [Assumption of Mary, hasTheologicalType, glorification of Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheologicalType Context triple: [Assumption of Mary, hasTheologicalType, glorification of Mary]
-
A.
theologicalCategory
chosen
Indicates the classification of something according to a particular theological type, tradition, or doctrinal category.
-
B.
hasTheologicalIssue
Indicates that one entity raises, involves, or is associated with a specific theological problem, concern, or point of doctrinal contention in relation to another entity.
-
C.
theologicalBelief
Indicates that one entity holds or endorses a specific religious or theological doctrine, view, or set of beliefs about the divine or spiritual matters.
-
D.
hasTheologicalPurpose
Indicates that something is intended or designed to serve a religious or theological function or goal.
-
E.
hasClergyType
Indicates the specific category or role of clergy associated with an entity.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc1f6d9c8190845d2fcd15fcdfd6 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.