Triple
T30915291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark Civil Aviation Complex |
E787561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aviation complex |
C36245
|
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 complex Context triple: [Clark Civil Aviation Complex, instanceOf, aviation complex]
-
A.
aviation infrastructure network
An aviation infrastructure network is an interconnected system of airports, airways, navigation aids, communication systems, and support facilities that collectively enable the safe, efficient movement of aircraft and passengers.
-
B.
aircraft factory
An aircraft factory is an industrial facility where aircraft and their components are designed, manufactured, assembled, and tested before delivery to customers.
-
C.
aviation infrastructure organization
chosen
An aviation infrastructure organization is an entity responsible for planning, developing, operating, and maintaining the physical and technological systems that support air transportation, such as airports, air traffic control, and related facilities.
-
D.
aviation attraction
An aviation attraction is a location, exhibit, or experience designed to engage visitors with aircraft, flight history, and aeronautical technology through displays, demonstrations, or interactive activities.
-
E.
aviation infrastructure plan
An aviation infrastructure plan is a strategic blueprint that outlines the development, expansion, maintenance, and integration of airport facilities, airspace systems, and supporting services to safely and efficiently meet current and future air transportation needs.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.