Triple
T28657848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | God Over All |
E725380
|
entity |
| Predicate | worldviewDefended |
P40990
|
FINISHED |
| Object | Christian theism |
—
|
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: Christian theism | Statement: [God Over All, worldviewDefended, Christian theism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldviewDefended Context triple: [God Over All, worldviewDefended, Christian theism]
-
A.
worldview
Indicates the overarching perspective or framework through which an entity interprets and understands the world and its experiences.
-
B.
worldviewImplication
Indicates that one worldview concept entails, suggests, or has consequences for another worldview concept or belief.
-
C.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
defendsConcept
chosen
Indicates that one entity actively supports and argues in favor of a particular concept, idea, or theory, often in response to criticism or challenge.
-
E.
defendsPosition
Indicates that one entity actively supports and justifies a stance, claim, or viewpoint in response to challenge or opposition.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 4:56 a.m.