Triple
T20681817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACP-EU Joint Parliamentary Assembly |
E508309
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ACP–EU institution |
C14427
|
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: ACP–EU institution Context triple: [ACP-EU Joint Parliamentary Assembly, instanceOf, ACP–EU institution]
-
A.
pro-European organization
A pro-European organization is a group that actively supports and promotes European integration, cooperation, and the values and policies of European institutions such as the European Union.
-
B.
European Union body
A European Union body is an institution, agency, or other organizational entity established by the EU’s founding treaties or secondary legislation to perform specific political, regulatory, advisory, or administrative functions within the Union’s governance framework.
-
C.
EU–US body
A formal, institutionalized entity that facilitates structured political, economic, and regulatory dialogue and cooperation between the European Union and the United States.
-
D.
European organisation
chosen
A European organisation is an entity based in or primarily serving Europe that coordinates activities, policies, or services across multiple European countries or within a specific European nation.
-
E.
European intergovernmental organization
A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:45 a.m.