Triple
T22723221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spokane Airport Board |
E561920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional airport authority |
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: regional airport authority Context triple: [Spokane Airport Board, instanceOf, regional airport authority]
-
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.
regional aviation organization
A regional aviation organization is an entity that coordinates, regulates, and promotes air transport services and infrastructure within a specific geographic area to ensure safe, efficient, and sustainable aviation operations.
-
C.
aviation infrastructure organization
An aviation infrastructure organization is an entity responsible for planning, developing, operating, and maintaining the physical and technological systems that support air transportation, such as airports, air traffic control, and related facilities.
-
D.
aviation authority
An aviation authority is a governmental or regulatory body responsible for overseeing civil aviation safety, security, standards, and compliance within a specific jurisdiction.
-
E.
airport economic zone
An airport economic zone is a designated area surrounding an airport where policies, infrastructure, and incentives are concentrated to attract businesses, promote trade, and stimulate regional economic development linked to air transport.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:20 p.m.