Triple
T12550295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SYRIZA |
E300078
|
entity |
| Predicate | becameUnitaryParty |
P7838
|
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, becameUnitaryParty, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameUnitaryParty Context triple: [SYRIZA, becameUnitaryParty, 2012]
-
A.
wasUnifiedWith
chosen
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
B.
reorganizedAsUnicameralIn
Indicates that a previously different legislative structure was changed into a unicameral (single-chamber) system in a specified place or time.
-
C.
hasUnitaryAuthority
Indicates that one entity serves as the single, primary governing or administrative authority over another entity or area.
-
D.
formedUnit
Indicates that one entity has been organized or constituted into a specific unit or group, establishing a formal unit-level relationship between them.
-
E.
unificationAct
Indicates the formal joining or merging of previously separate entities into a single unified whole.
- 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.