Triple
T28195794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groundforce |
E716443
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport ground handling company |
C15604
|
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: airport ground handling company Context triple: [Groundforce, instanceOf, airport ground handling company]
-
A.
ground handling company
chosen
A ground handling company is a service provider that manages aircraft and passenger support operations at airports, including baggage handling, ramp services, check-in, and aircraft servicing on the ground.
-
B.
airport services provider
An airport services provider is an organization that delivers ground handling, passenger assistance, cargo management, and related operational support services to airlines and airport authorities.
-
C.
airport consultancy company
A specialized professional services firm that advises airports and aviation stakeholders on planning, design, operations, strategy, and regulatory compliance to optimize performance and growth.
-
D.
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.
-
E.
air transport service provider
An air transport service provider is an organization that offers the commercial operation, management, and coordination of aircraft and related services to move passengers or cargo between locations.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 10:27 p.m.