Triple
T25378450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamoussoukro Decision |
E633114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation agreement |
C41428
|
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: aviation agreement Context triple: [Yamoussoukro Decision, instanceOf, aviation agreement]
-
A.
aviation convention
An aviation convention is a large organized gathering of aviation professionals, enthusiasts, and industry stakeholders to showcase aircraft, technologies, services, and to exchange knowledge through exhibitions, presentations, and networking events.
-
B.
aviation liability convention
chosen
An aviation liability convention is an international legal agreement that standardizes rules for airlines’ financial responsibility and compensation for passengers, cargo, and third parties in the event of accidents or incidents in air transport.
-
C.
aviation law
Aviation law is the body of rules, regulations, and international agreements that govern the operation, safety, security, and economic aspects of air travel and aircraft use.
-
D.
aviation policy initiative
An aviation policy initiative is a coordinated effort, typically led by governments or industry bodies, to develop, reform, or implement rules and strategies that shape the safety, efficiency, sustainability, and economic regulation of air transport systems.
-
E.
bilateral military agreement
A bilateral military agreement is a formal pact between two states that outlines mutual defense commitments, security cooperation, and related military obligations and activities.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:38 p.m.