Triple
T25171280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Passenger Protection Regulations |
E630328
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | passenger rights regime |
C49834
|
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: passenger rights regime Context triple: [Air Passenger Protection Regulations, instanceOf, passenger rights regime]
-
A.
aviation liability convention
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.
-
B.
transportation safety law
Transportation safety law is the body of legal rules and regulations designed to prevent accidents and injuries in all modes of transport by setting safety standards, enforcing compliance, and assigning liability for violations.
-
C.
IATA resolution
An IATA resolution is an official, standardized rule or agreement adopted by the International Air Transport Association that governs specific aspects of airline operations, procedures, or commercial practices across member carriers.
-
D.
passenger facility
A passenger facility is a designated area or building that provides services, amenities, and access points to support the boarding, alighting, and transit needs of travelers using a transportation system.
-
E.
carriage of goods by sea regime
A carriage of goods by sea regime is a legal framework that governs the rights, obligations, and liabilities of carriers and cargo interests in the international transport of goods by sea.
- F. None of above. chosen
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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
Created at: April 21, 2026, 12:20 p.m.