Triple

T4086781
Position Surface form Disambiguated ID Type / Status
Subject Progressive Party (United States, 1912) E87605 entity
Predicate causedEffect P694 FINISHED
Object split Republican vote in 1912 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: split Republican vote in 1912 | Statement: [Progressive Party (United States, 1912), causedEffect, split Republican vote in 1912]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: causedEffect
Context triple: [Progressive Party (United States, 1912), causedEffect, split Republican vote in 1912]
  • A. causeOf chosen
    Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
  • B. causeOfAction
    Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
  • C. tookEffect
    Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
  • D. sideEffect
    Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
  • E. causeSupported
    Indicates that an entity provides backing, endorsement, or assistance to a particular cause or initiative.
  • 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_69aed94425148190be337845d56fac22 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefc7ceeb48190807f0f5078ccfa12 completed March 9, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69aef909c9c88190b09d48dad325a83c completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:39 p.m.