Triple
T28226463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Anti-Capitalist Left |
E711600
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transnational political alliance |
C13943
|
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: transnational political alliance Context triple: [European Anti-Capitalist Left, instanceOf, transnational political alliance]
-
A.
political-military alliance
A political-military alliance is a formal agreement between two or more states to coordinate their defense and foreign policies, often including mutual security guarantees and joint military planning.
-
B.
transnational organization
chosen
A transnational organization is an entity that operates across multiple countries, coordinating activities, resources, and decision-making beyond the authority or boundaries of any single nation-state.
-
C.
European political alliance
A European political alliance is a cooperative grouping of political parties or states within Europe that coordinate policies, strategies, and actions to advance shared ideological or strategic interests across national borders.
-
D.
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.
-
E.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 10:50 p.m.