Triple
T36471997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit-fighters |
E898560
|
entity |
| Predicate | hasDoctrinalErrorType |
P144597
|
FINISHED |
| Object | anti-Trinitarianism |
—
|
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: anti-Trinitarianism | Statement: [Spirit-fighters, hasDoctrinalErrorType, anti-Trinitarianism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoctrinalErrorType Context triple: [Spirit-fighters, hasDoctrinalErrorType, anti-Trinitarianism]
-
A.
hasDoctrinalTest
Indicates that an entity is subject to, or associated with, a specific doctrinal test or examination of beliefs.
-
B.
hasErrorType
chosen
Indicates that an entity is associated with, or classified by, a specific type or category of error.
-
C.
hasDoctrinalStandardInPart
Indicates that one entity possesses or upholds a specific doctrinal standard within a particular section or component of itself.
-
D.
hasDoctrinalDifferencesIn
Indicates that there are differences in doctrine or beliefs between entities within a specified domain or context.
-
E.
hasDoctrinalCharacteristic
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:10 p.m.