Triple
T158189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tritheism |
E3223
|
entity |
| Predicate | violates |
P2111
|
FINISHED |
| Object | doctrine of divine simplicity |
—
|
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: doctrine of divine simplicity | Statement: [Tritheism, violates, doctrine of divine simplicity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violates Context triple: [Tritheism, violates, doctrine of divine simplicity]
-
A.
violatedPrinciple
chosen
Indicates that an entity has broken, disregarded, or acted contrary to a specified rule, norm, or guiding principle.
-
B.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
C.
discourages
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
D.
neglects
Indicates a relationship where one party fails to give appropriate attention, care, or consideration to another party or responsibility.
-
E.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.