Triple
T30915652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan–Philippines air travel market |
E787571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international air travel market |
C60353
|
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: international air travel market Context triple: [Japan–Philippines air travel market, instanceOf, international air travel market]
-
A.
international air route
An international air route is a designated flight path that connects airports in different countries, governed by bilateral or multilateral agreements and aviation regulations.
-
B.
international airport
An international airport is a large, complex transportation hub that facilitates the arrival, departure, and transfer of passengers and cargo between countries through scheduled and chartered flights, customs, immigration, and related services.
-
C.
transatlantic flight
A transatlantic flight is a commercial or private air journey that crosses the Atlantic Ocean, typically connecting cities in North America with those in Europe, Africa, or South America.
-
D.
air transport connection
An air transport connection is a scheduled or unscheduled linkage between two or more locations by aircraft, enabling the movement of passengers or cargo within an air transportation network.
-
E.
international aviation infrastructure component
An international aviation infrastructure component is a physical or digital asset—such as airports, air traffic control systems, navigation aids, or communication networks—that enables the safe, efficient, and coordinated operation of cross-border air transport.
- F. None of above. chosen
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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.