Triple
T10000751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney global maintenance network |
E197318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | aerospace support network |
C5661
|
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: aerospace support network Context triple: [Pratt & Whitney global maintenance network, instanceOf, aerospace support network]
-
A.
aerospace corporation
An aerospace corporation is a large-scale enterprise that designs, manufactures, and services aircraft, spacecraft, and related systems and technologies for commercial, military, and space applications.
-
B.
NASA ground support equipment
NASA ground support equipment comprises the specialized tools, structures, and systems used on the ground to assemble, test, transport, service, and launch spacecraft and launch vehicles safely and reliably.
-
C.
aerospace organization
chosen
An aerospace organization is an entity that researches, designs, manufactures, operates, or supports aircraft, spacecraft, and related systems and technologies for commercial, governmental, or defense purposes.
-
D.
aerospace hub
An aerospace hub is a centralized facility or region where aerospace research, manufacturing, testing, and logistics activities are concentrated to support the development and operation of aircraft and spacecraft.
-
E.
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.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:51 p.m.