Triple
T404994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | God the Father |
E9363
|
entity |
| Predicate | isRelatedToDoctrine |
P5485
|
FINISHED |
| Object | doctrine of the Trinity |
—
|
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 the Trinity | Statement: [God the Father, isRelatedToDoctrine, doctrine of the Trinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedToDoctrine Context triple: [God the Father, isRelatedToDoctrine, doctrine of the Trinity]
-
A.
usesDoctrine
Indicates that one entity applies, follows, or relies on a particular doctrine in its actions or reasoning.
-
B.
concernsDoctrine
chosen
Indicates that something is related or pertains specifically to a particular doctrine or set of doctrinal principles.
-
C.
keyDoctrine
Indicates that something is a central or foundational doctrine within a belief system, organization, or theoretical framework.
-
D.
teachesDoctrine
Indicates that one entity imparts, explains, or promotes a specific doctrine or set of beliefs to another entity.
-
E.
deniesDoctrine
Indicates that one entity rejects, opposes, or refuses to accept the truth or validity of a particular doctrine associated with another entity.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eca37fe881909802126952dfdd59 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.