Triple
T12633701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotism |
E301705
|
entity |
| Predicate | hasViewOnGod |
P5768
|
FINISHED |
| Object | God as infinite being |
—
|
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 as infinite being | Statement: [Scotism, hasViewOnGod, God as infinite being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnGod Context triple: [Scotism, hasViewOnGod, God as infinite being]
-
A.
viewOnGod
chosen
Indicates a relationship where one entity holds or expresses a particular opinion, belief, or perspective about God.
-
B.
viewOfGod
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
-
C.
viewOnSeeingGod
Indicates a stance or interpretation someone holds regarding the experience or possibility of seeing God.
-
D.
hasViewOnDivinity
Indicates that an entity holds a particular belief, opinion, or perspective regarding divinity or the nature of the divine.
-
E.
viewOfGodhead
Indicates a relationship where an entity holds or expresses a particular understanding, perspective, or doctrinal stance regarding the nature or composition of the Godhead.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:15 p.m.