Triple
T21817354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU–Japan industrial cooperation centre |
E538636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint EU–Japan institution |
C43630
|
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: joint EU–Japan institution Context triple: [EU–Japan industrial cooperation centre, instanceOf, joint EU–Japan institution]
-
A.
joint organization
chosen
A joint organization is a collaborative entity formed by two or more independent parties that share resources, responsibilities, and decision-making to achieve common objectives.
-
B.
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.
-
C.
joint British–Irish institution
A joint British–Irish institution is an organization or body formally established and operated by both the United Kingdom and Ireland to manage shared interests, cooperation, or governance across their mutual areas of concern.
-
D.
European organisation
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.
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.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:54 p.m.