Triple
T13249311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE Aviation global MRO network |
E315485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation support network |
C21084
|
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: aviation support network Context triple: [GE Aviation global MRO network, instanceOf, aviation support network]
-
A.
aviation infrastructure network
chosen
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.
-
B.
aviation support battalion
An aviation support battalion is a military unit that provides maintenance, logistics, supply, and technical support to aviation brigades to ensure continuous, effective air operations.
-
C.
naval air station
A naval air station is a military airfield operated by a navy, providing facilities for the operation, maintenance, training, and support of naval aircraft and their personnel.
-
D.
aviation infrastructure plan
An aviation infrastructure plan is a strategic blueprint that outlines the development, expansion, maintenance, and integration of airport facilities, airspace systems, and supporting services to safely and efficiently meet current and future air transportation needs.
-
E.
naval air service
A naval air service is a military aviation branch responsible for operating aircraft and related support units in direct support of a nation's navy, including maritime patrol, fleet air defense, anti-submarine warfare, and carrier-based operations.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:24 p.m.