Triple
T25579013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jet Aviation |
E641188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business aviation services company |
C25406
|
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: business aviation services company Context triple: [Jet Aviation, instanceOf, business aviation services company]
-
A.
business aviation company division
A business aviation company division is an organizational unit within a larger aviation enterprise that focuses on providing private air travel services, fleet management, and related support specifically for corporate and high-net-worth clients.
-
B.
aviation business
Aviation business encompasses the commercial activities and operations involved in providing air transportation services, including airlines, airports, aircraft manufacturing, maintenance, and related support industries.
-
C.
business aviation airport
A business aviation airport is a specialized airfield designed primarily to serve private, corporate, and charter aircraft with tailored facilities and services for business travelers.
-
D.
business aviation airport
A business aviation airport is a specialized airfield designed primarily to serve private, corporate, and charter aircraft with tailored facilities and services for non-scheduled, business-focused air travel.
-
E.
aviation management company
chosen
An aviation management company oversees and coordinates aircraft operations, maintenance, crew, regulatory compliance, and related services to ensure safe, efficient, and cost-effective aviation activities for clients.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 4:03 p.m.