Triple
T2623415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don Army |
E59060
|
entity |
| Predicate | opponentIdeology |
P18907
|
FINISHED |
| Object | Bolshevism |
—
|
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: Bolshevism | Statement: [Don Army, opponentIdeology, Bolshevism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentIdeology Context triple: [Don Army, opponentIdeology, Bolshevism]
-
A.
opposingIdeology
chosen
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
-
B.
mainIdeologue
Indicates that one entity serves as the primary theorist or chief ideological architect behind another entity’s beliefs, policies, or movement.
-
C.
ideology
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
D.
ideologicalRange
Indicates the span or spectrum of ideological positions or beliefs associated with an entity, typically from one end of a defined ideological scale to the other.
-
E.
hasIdeologicalPosition
Indicates that an entity holds, endorses, or is associated with a particular ideological stance or viewpoint.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.