Triple
T15258101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schiphol terminal piers system |
E364699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport infrastructure component |
C4129
|
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 infrastructure component Context triple: [Schiphol terminal piers system, instanceOf, airport infrastructure component]
-
A.
international aviation infrastructure component
An international aviation infrastructure component is a physical or digital asset—such as airports, air traffic control systems, navigation aids, or communication networks—that enables the safe, efficient, and coordinated operation of cross-border air transport.
-
B.
airport-related building
A building located on or near an airport that supports air travel operations, such as terminals, control towers, hangars, or maintenance facilities.
-
C.
airport system
chosen
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.
-
D.
airport runway
An airport runway is a long, specially prepared strip of land or pavement where aircraft take off and land, designed with specific markings, lighting, and surface strength to ensure safe operations.
-
E.
aviation infrastructure network
An aviation infrastructure network is an interconnected system of airports, airways, navigation aids, communication systems, and support facilities that collectively enable the safe, efficient movement of aircraft and passengers.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:13 a.m.