Triple

T33363787
Position Surface form Disambiguated ID Type / Status
Subject Socialist Reich Party E854293 entity
Predicate hadParamilitaryElements P4659 FINISHED
Object yes 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: yes | Statement: [Socialist Reich Party, hadParamilitaryElements, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadParamilitaryElements
Context triple: [Socialist Reich Party, hadParamilitaryElements, yes]
  • A. paramilitary chosen
    Indicates that an entity is associated with an organized, armed group that operates similarly to a military force but is not part of the official state military.
  • B. wasMilitarized
    Indicates that an entity underwent a process of being organized, equipped, or adapted for military use or purposes.
  • C. wasMilitarizedDuring
    Indicates that an entity transitioned to or adopted a military character, role, or control during a specified time period or event.
  • D. militaryForceUsed
    Indicates that one entity employs or applies military power or armed force against, within, or in relation to another entity or situation.
  • E. paramilitaryWing
    Indicates that one entity functions as the paramilitary or armed wing associated with another entity, typically an organization or movement.
  • 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_69f3496bda8c8190bfc8fade9d1b791c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e3156ea48190b604e414665ef351 completed May 3, 2026, 5:54 a.m.
PD Predicate disambiguation batch_69f6de0b9ba48190887c9eb5d06a2e94 completed May 3, 2026, 5:32 a.m.
Created at: May 1, 2026, 1:34 a.m.