Triple
T12032350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IATA Ground Operations Manual |
E286443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ground handling standard |
C28398
|
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: ground handling standard Context triple: [IATA Ground Operations Manual, instanceOf, ground handling standard]
-
A.
ground handling company
A ground handling company is a service provider that manages aircraft and passenger support operations at airports, including baggage handling, ramp services, check-in, and aircraft servicing on the ground.
-
B.
ICAO standard
An ICAO standard is an internationally agreed set of rules, specifications, and recommended practices established by the International Civil Aviation Organization to ensure the safety, regularity, and efficiency of global civil aviation.
-
C.
air transport industry standard
chosen
A formalized set of rules, guidelines, and technical specifications that ensure safety, interoperability, efficiency, and regulatory compliance across the global air transport industry.
-
D.
implementation mechanism for ICAO Standards and Recommended Practices
A structured set of legal, administrative, and technical processes through which States adopt, adapt, and apply ICAO Standards and Recommended Practices within their national civil aviation systems.
-
E.
transportation standard
A transportation standard is an agreed-upon set of rules, specifications, and protocols that ensure compatibility, safety, and efficiency across transportation systems, vehicles, and infrastructure.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.