Triple

T12992799
Position Surface form Disambiguated ID Type / Status
Subject GA3 E321956 entity
Predicate typicalPartisanLeaning P15842 FINISHED
Object Republican-leaning 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: Republican-leaning | Statement: [GA3, typicalPartisanLeaning, Republican-leaning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalPartisanLeaning
Context triple: [GA3, typicalPartisanLeaning, Republican-leaning]
  • A. politicalTendency chosen
    Indicates the general political orientation, leaning, or ideological stance associated with an entity in relation to the political spectrum.
  • B. hasStrongPartyLean
    Indicates that an entity consistently favors or aligns strongly with a particular political party.
  • C. politicalSide
    Indicates the political alignment or ideological position that one entity holds in relation to political spectra or groupings.
  • D. nonPartisan
    Indicates that an entity is not affiliated with, influenced by, or acting on behalf of any political party or partisan interest.
  • E. traditionalPoliticalAlignment
    Indicates how closely an entity’s political views or affiliations align with established, historically dominant, or customary political positions within a given context.
  • 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_69d8076479b8819090afce3591939cdf completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97f2a71a0819098bb6cf8a4b2208a completed April 10, 2026, 10:52 p.m.
PD Predicate disambiguation batch_69d97dbdd94c8190ac4bbecca02dc77b completed April 10, 2026, 10:46 p.m.
Created at: April 9, 2026, 8:44 p.m.