Triple
T3964293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ash'ari |
E85977
|
entity |
| Predicate | viewOnDivineWill |
P5608
|
FINISHED |
| Object | God's will is absolute |
—
|
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: God's will is absolute | Statement: [Ash'ari, viewOnDivineWill, God's will is absolute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnDivineWill Context triple: [Ash'ari, viewOnDivineWill, God's will is absolute]
-
A.
viewOnGod
Indicates a relationship where one entity holds or expresses a particular opinion, belief, or perspective about God.
-
B.
hasViewOnDivinity
chosen
Indicates that an entity holds a particular belief, opinion, or perspective regarding divinity or the nature of the divine.
-
C.
viewOfGod
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
-
D.
viewOnSoul
Indicates a relationship where one entity holds or expresses a particular perspective, belief, or stance regarding the nature, existence, or characteristics of the soul.
-
E.
viewOfWill
Indicates a relationship where something represents, expresses, or reflects the will, intention, or volition of an agent.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.