Triple
T6497145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekthesis |
E148785
|
entity |
| Predicate | christologicalFormula |
P15107
|
FINISHED |
| Object | one will in Christ |
—
|
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: one will in Christ | Statement: [Ekthesis, christologicalFormula, one will in Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: christologicalFormula Context triple: [Ekthesis, christologicalFormula, one will in Christ]
-
A.
hasChristologicalUse
Indicates that something is used or interpreted in a way that relates specifically to the person, nature, or work of Christ within Christian theology.
-
B.
incarnationOf
Indicates that one entity is a concrete embodiment, manifestation, or earthly form of another, typically more abstract or divine, entity.
-
C.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
D.
theologicalConcept
chosen
Indicates that something is a religious or theological idea, doctrine, or principle within a belief system.
-
E.
emphasizesAttributeOfChrist
Indicates that something highlights, underscores, or draws special attention to a particular attribute or quality of Christ.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:41 p.m.