Triple
T1847435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka International Airport Terminal Co., Ltd. |
E41315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport terminal operator |
C1049
|
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: airport terminal operator Context triple: [Osaka International Airport Terminal Co., Ltd., instanceOf, airport terminal operator]
-
A.
airport authority
chosen
An airport authority is an organization responsible for the ownership, management, operation, and regulation of an airport or group of airports, ensuring safe, efficient, and compliant aviation services and facilities.
-
B.
airport system
An airport system is an integrated network of facilities, services, and processes that manages the safe, efficient movement of passengers, cargo, and aircraft within and around an airport.
-
C.
international terminal area
An international terminal area is a designated section of an airport where passengers check in, depart, arrive, and transit for international flights, including associated facilities such as customs, immigration, security, and boarding gates.
-
D.
cargo airport
A cargo airport is a specialized aviation facility designed primarily for the handling, storage, and transportation of freight and mail, featuring extensive logistics infrastructure and limited or no passenger services.
-
E.
airport shuttle service
An airport shuttle service is a transportation operation that provides scheduled or on-demand rides between airports and surrounding locations such as hotels, parking facilities, and city centers.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:33 p.m.