Triple

T33786792
Position Surface form Disambiguated ID Type / Status
Subject III Государственная дума Российской империи E865812 entity
Predicate reasonForNewElectoralLaw P51946 FINISHED
Object разгон II Государственной думы 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: разгон II Государственной думы | Statement: [III Государственная дума Российской империи, reasonForNewElectoralLaw, разгон II Государственной думы]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForNewElectoralLaw
Context triple: [III Государственная дума Российской империи, reasonForNewElectoralLaw, разгон II Государственной думы]
  • A. byElectionReason
    Indicates the reason or cause for which a by-election is being held.
  • B. changedElectoralSystem
    Indicates that an entity has altered or replaced a previously existing electoral system with a different one.
  • C. reasonForNewPresident
    Indicates the circumstance, cause, or justification that led to the appointment or election of a new president.
  • D. electoralReformContext chosen
    Indicates the context or circumstances related to changes or proposed changes in an electoral system or voting rules.
  • E. electoralSystemConcerned
    Indicates that something is related to, affected by, or focused on a particular electoral 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_69f3498ecc2c8190bcd85e3f11dc215e completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fd6a1c1c4881908090053bc359b181 completed May 8, 2026, 4:44 a.m.
PD Predicate disambiguation batch_69fd696f24d8819091033afacbdaadc5 completed May 8, 2026, 4:41 a.m.
Created at: May 1, 2026, 1:45 a.m.