Triple
T28477084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enosis movements in Cyprus |
E720591
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unionist movement |
C42410
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: unionist movement Context triple: [Enosis movements in Cyprus, instanceOf, unionist movement]
-
A.
unionist organization
chosen
A unionist organization is a group that advocates for maintaining or strengthening political, economic, or social unity between regions, states, or nations, often opposing movements for separation or independence.
-
B.
unionism
Unionism is the advocacy and practice of organizing workers into unions to collectively negotiate for better wages, conditions, and rights, or, in a political context, the support for maintaining or forming a political union between regions or states.
-
C.
political union
A political union is a formal association of two or more political entities that share or merge governance structures to coordinate policies, laws, and collective decision-making.
-
D.
union republic
A union republic is a constituent political unit within a federal or quasi-federal state, typically possessing its own government and constitution while remaining subordinate to the overarching union authority.
-
E.
White movement polity
A White movement polity is a provisional or semi-formal governmental entity established by anti-Bolshevik forces during the Russian Civil War, typically claiming to represent a unified, non-communist Russian state while exercising varying degrees of military and civil authority over contested territories.
- F. None of above.
Provenance (1 batch)
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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 2:53 a.m.