Triple
T27669710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travelport |
E697626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global distribution system |
C23274
|
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: global distribution system Context triple: [Travelport, instanceOf, global distribution system]
-
A.
global distribution system provider
chosen
A global distribution system provider is a company that operates a computerized network enabling transactions between travel service suppliers (such as airlines, hotels, and car rental companies) and travel agencies or end customers worldwide.
-
B.
storage and distribution system
A storage and distribution system is an integrated arrangement of facilities, equipment, and processes designed to efficiently receive, store, manage, and deliver goods or resources to their intended destinations.
-
C.
global network
A global network is a worldwide interconnected system of communication and information exchange that links devices, organizations, and individuals across international boundaries.
-
D.
logistics network
A logistics network is an interconnected system of facilities, transportation modes, and information flows designed to efficiently move goods from origin to destination while optimizing cost, time, and service quality.
-
E.
global communication system
A global communication system is an interconnected network of technologies, protocols, and infrastructures that enables real-time exchange of information across the world regardless of geographic location.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:40 p.m.