Triple
T36472046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Spirit as ‘Lord and giver of life’ |
E898561
|
entity |
| Predicate | guardsAgainst |
P6876
|
FINISHED |
| Object | denial of the Spirit’s full divinity |
—
|
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: denial of the Spirit’s full divinity | Statement: [Holy Spirit as ‘Lord and giver of life’, guardsAgainst, denial of the Spirit’s full divinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardsAgainst Context triple: [Holy Spirit as ‘Lord and giver of life’, guardsAgainst, denial of the Spirit’s full divinity]
-
A.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
-
B.
armedAgainst
Indicates that one entity is equipped with weapons or defensive capabilities specifically in preparation for potential conflict with another entity.
-
C.
defends
chosen
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
guardFeature
Indicates that one entity protects, secures, or restricts access to a particular feature of another entity.
-
E.
builtToDefendAgainst
Indicates that something was constructed or designed specifically for the purpose of protecting against or countering a particular threat, entity, or type of attack.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.