Triple
T10535017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Byzantine theology |
E248539
|
entity |
| Predicate | goalOfSpiritualLife |
P60492
|
FINISHED |
| Object | union with God |
—
|
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: union with God | Statement: [Byzantine theology, goalOfSpiritualLife, union with God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfSpiritualLife Context triple: [Byzantine theology, goalOfSpiritualLife, union with God]
-
A.
spiritualMeans
Indicates that one entity serves as a spiritual method, medium, or pathway through which another entity attains or engages in a spiritual state, goal, or practice.
-
B.
spiritualQuest
Indicates a process in which an entity actively seeks deeper spiritual understanding, growth, or enlightenment.
-
C.
goalOfWorship
Indicates that one entity is the intended object or focus of another entity’s worship or devotional practice.
-
D.
spiritualBenefit
Indicates a relationship where one entity provides, enhances, or is associated with a positive spiritual gain, growth, or advantage for another entity.
-
E.
spiritualAchievement
chosen
Indicates the attainment or realization of a significant level of spiritual growth, insight, or enlightenment by 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a1b20d48190a51358ec1af80371 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:31 p.m.