Triple
T3765871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAV Airports |
E82675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation services company |
C4916
|
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 services company Context triple: [TAV Airports, instanceOf, aviation services company]
-
A.
private aviation company
A private aviation company provides personalized, on-demand air travel services using owned or managed aircraft for individuals, businesses, or charter clients.
-
B.
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.
-
C.
airline holding company
An airline holding company is a parent corporation that owns and controls one or more airline carriers and related aviation businesses, managing strategy and finances while allowing the individual airlines to operate with some autonomy.
-
D.
transportation services company
chosen
A transportation services company is an organization that plans, manages, and operates the movement of people or goods using various modes of transport, such as road, rail, air, or sea, often providing logistics, scheduling, and support services.
-
E.
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.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.