Triple
T28658059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Doctrine of the Holy Spirit |
E725386
|
entity |
| Predicate | exploresDoctrine |
P85544
|
FINISHED |
| Object | Trinity |
—
|
NE NERFINISHED |
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: Trinity | Statement: [The Doctrine of the Holy Spirit, exploresDoctrine, Trinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresDoctrine Context triple: [The Doctrine of the Holy Spirit, exploresDoctrine, Trinity]
-
A.
examinesDoctrine
chosen
Indicates that one entity critically studies, analyzes, or evaluates a particular doctrine or set of beliefs.
-
B.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
C.
developedDoctrine
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
-
D.
currentDoctrine
Indicates the doctrine, policy, or set of guiding principles that is presently in force or officially adopted at a given time.
-
E.
illustratesDoctrine
Indicates that one entity serves as an example or demonstration that clarifies, explains, or supports a particular doctrine or set of principles in 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 4:56 a.m.