Triple
T12550301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SYRIZA |
E300078
|
entity |
| Predicate | electoralBreakthroughYear |
P69741
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [SYRIZA, electoralBreakthroughYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralBreakthroughYear Context triple: [SYRIZA, electoralBreakthroughYear, 2012]
-
A.
firstDemocraticFlipYear
Indicates the first year in which an entity (such as a region or seat) changed from non-Democratic to Democratic control or outcome.
-
B.
notableElectionYear
chosen
Indicates that a particular year is recognized as significant or noteworthy in the context of an election involving the given entity.
-
C.
firstElectionYear
Indicates the calendar year in which an entity (such as a person, office, or political body) first participated in or was subject to an election.
-
D.
electoralCollapseYear
Indicates the year in which an electoral system, party, or coalition experienced a decisive collapse or breakdown in its electoral support or functioning.
-
E.
reElectionYear
Indicates the year in which an entity is (or is scheduled to be) elected again to the same position or office.
- 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.