Triple

T2847881
Position Surface form Disambiguated ID Type / Status
Subject Omnipotent Government E63023 entity
Predicate positionOnFascism P43394 FINISHED
Object critical 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: critical | Statement: [Omnipotent Government, positionOnFascism, critical]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionOnFascism
Context triple: [Omnipotent Government, positionOnFascism, critical]
  • A. opposingIdeology
    Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
  • B. positionOnFreedom
    Indicates a stance or viewpoint an entity holds regarding the concept, extent, or conditions of freedom.
  • C. politicalBlocOnOtherSide
    Indicates that one political bloc is positioned in opposition to, or on the opposing side of, another political bloc within a political context.
  • D. enforcedIdeology
    Indicates that one entity compels another to adopt, follow, or conform to a particular set of beliefs or ideology, typically through authority, pressure, or coercive means.
  • E. positionOnEvil
    Indicates a stance or viewpoint an entity holds regarding what is considered evil or morally wrong.
  • F. None of above. chosen

Provenance (4 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_69ab4c407c408190857d25e027155ce9 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf403698819084fb4ace5839aa05 completed March 7, 2026, 8:18 a.m.
PD Predicate disambiguation batch_69abdd0e86808190bcefffafbd3cd441 completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abde2cdcc48190827195d3ae70aa19 completed March 7, 2026, 8:13 a.m.
Created at: March 6, 2026, 10:02 p.m.