Triple
T23343980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metapolitefsi |
E591805
|
entity |
| Predicate | politicalChangeType |
P19691
|
FINISHED |
| Object | transition to democracy |
—
|
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: transition to democracy | Statement: [Metapolitefsi, politicalChangeType, transition to democracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalChangeType Context triple: [Metapolitefsi, politicalChangeType, transition to democracy]
-
A.
politicalShift
Indicates a change in an entity’s political position, alignment, or governing structure over time.
-
B.
electionChange
Indicates a change in the outcome, status, or key parameters of an election between two points in time.
-
C.
constitutionalChange
Indicates a formal modification, addition, or removal of provisions within a constitution or foundational legal framework.
-
D.
typeOfRegimeChange
chosen
Indicates a change in the form, structure, or governing system of a political regime, such as transitions between different types of rule or authority.
-
E.
changedElectoralSystem
Indicates that an entity has altered or replaced a previously existing electoral system with a different one.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198358fb8819094c74cfd53cbab44 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:18 p.m.