Triple
T17478826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention for the Suppression of Unlawful Acts against the Safety of Civil Aviation |
E425605
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation security treaty |
C566
|
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 security treaty Context triple: [Convention for the Suppression of Unlawful Acts against the Safety of Civil Aviation, instanceOf, aviation security treaty]
-
A.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
aviation security list
An aviation security list is an official roster of individuals or entities identified as potential threats to civil aviation, used to screen and restrict their access to flights, airports, or related services.
-
C.
transportation security agency
A transportation security agency is an organization responsible for protecting transportation systems and infrastructure by preventing and responding to security threats to passengers, cargo, and facilities.
-
D.
airspace security operation
An airspace security operation is a coordinated set of activities, technologies, and procedures designed to monitor, control, and protect designated airspace from unauthorized or hostile aerial threats.
-
E.
aircraft hijacking
Aircraft hijacking is the unlawful seizure and control of an aircraft in flight, typically by force or threat, to coerce authorities, achieve political or criminal objectives, or endanger passengers and crew.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:48 a.m.