Triple
T23394103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aviation Technical Services |
E594101
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aircraft maintenance, repair, and overhaul provider |
C28044
|
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: aircraft maintenance, repair, and overhaul provider Context triple: [Aviation Technical Services, instanceOf, aircraft maintenance, repair, and overhaul provider]
-
A.
maintenance, repair and overhaul provider
A maintenance, repair and overhaul provider is an organization that performs inspection, servicing, repair, and refurbishment of equipment or systems to ensure their continued safe, reliable, and efficient operation.
-
B.
aircraft maintenance company
chosen
An aircraft maintenance company is an organization that inspects, repairs, overhauls, and services aircraft and their components to ensure safety, reliability, and regulatory compliance.
-
C.
air-to-air refuelling service provider
An air-to-air refuelling service provider is an organization that operates tanker aircraft and associated support systems to deliver in-flight fuel to receiver aircraft, extending their range, endurance, and mission effectiveness.
-
D.
aerostructures manufacturer
An aerostructures manufacturer designs, engineers, and produces critical aircraft structural components—such as fuselages, wings, and empennages—for commercial, military, and aerospace applications.
-
E.
aircraft engine manufacturer
An aircraft engine manufacturer is a company that designs, develops, produces, and supports engines specifically for use in airplanes and other aircraft.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:36 p.m.