Triple
T3599644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macarius of Antioch |
E76223
|
entity |
| Predicate | christologicalView |
P10112
|
FINISHED |
| Object | Christ has one will |
—
|
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: Christ has one will | Statement: [Macarius of Antioch, christologicalView, Christ has one will]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: christologicalView Context triple: [Macarius of Antioch, christologicalView, Christ has one will]
-
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.
viewOnChrist
chosen
Indicates a person's stance, belief, or perspective regarding Jesus Christ.
-
C.
regardsJesusAs
Indicates that one entity holds a particular view, attitude, or evaluation of Jesus as another entity.
-
D.
viewOnCreeds
Indicates a relationship where one party holds or expresses a particular stance, opinion, or interpretation regarding a set of creeds or formal beliefs.
-
E.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc19fd57481908ce5c9daf168e213 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.