Triple
T12550299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SYRIZA |
E300078
|
entity |
| Predicate | principalRivalIdeology |
P77419
|
FINISHED |
| Object | center-right |
—
|
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: center-right | Statement: [SYRIZA, principalRivalIdeology, center-right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalRivalIdeology Context triple: [SYRIZA, principalRivalIdeology, center-right]
-
A.
notableOpponentIdeology
chosen
Indicates that an entity’s notable opponent is associated with, represents, or is characterized by a particular ideology.
-
B.
politicalRivalOf
Indicates a relationship in which two political actors or groups compete against or oppose each other for power, influence, or office.
-
C.
opposingIdeology
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
-
D.
rivalParty
Indicates that one party is in competition or opposition with another party, often pursuing conflicting goals or interests.
-
E.
primaryOpposingLeader
Indicates that one entity serves as the main or chief leader directly opposing another entity in a conflict, competition, or political 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:58 p.m.