Triple
T27465928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Committee for air transport between EU and US |
E693177
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EU–US joint body |
C22902
|
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: EU–US joint body Context triple: [Joint Committee for air transport between EU and US, instanceOf, EU–US joint body]
-
A.
EU–US body
chosen
A formal, institutionalized entity that facilitates structured political, economic, and regulatory dialogue and cooperation between the European Union and the United States.
-
B.
U.S.–Canada joint body
A U.S.–Canada joint body is a binational institution established by the United States and Canada to coordinate, manage, or regulate shared interests such as natural resources, trade, security, or environmental protection across their common border.
-
C.
UK–EU body
A UK–EU body is a joint institutional entity established by agreements between the United Kingdom and the European Union to oversee, implement, or manage specific aspects of their bilateral relationship.
-
D.
EU–Japan cooperation mechanism
The EU–Japan cooperation mechanism is an institutional framework that coordinates political dialogue, economic partnership, and sectoral collaboration between the European Union and Japan to address shared strategic, regulatory, and global challenges.
-
E.
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.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 12:52 p.m.