Triple
T35476943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasmanian regional aviation network |
E1025360
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional aviation network |
C31875
|
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 aviation network Context triple: [Tasmanian regional aviation network, instanceOf, regional aviation network]
-
A.
regional flight system
A regional flight system manages the scheduling, routing, and operation of short- to medium-haul flights within a specific geographic area, coordinating aircraft, crew, airports, and passenger services.
-
B.
regional air route
chosen
A regional air route is a defined flight path connecting airports within a specific geographic area, typically served by short- to medium-haul aircraft to facilitate local or intra-regional air travel.
-
C.
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.
-
D.
regional aviation industry
The regional aviation industry encompasses airlines, airports, manufacturers, and service providers that operate and support short- to medium-haul air transport connecting smaller cities and communities to larger hubs.
-
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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.