Triple
T10000750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratt & Whitney global maintenance network |
E197318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maintenance, repair and overhaul network |
C27275
|
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: maintenance, repair and overhaul network Context triple: [Pratt & Whitney global maintenance network, instanceOf, maintenance, repair and overhaul network]
-
A.
network operations facility
A network operations facility is a centralized, secure environment where personnel and systems monitor, manage, and maintain an organization’s communication networks and related infrastructure to ensure reliable, efficient, and secure operations.
-
B.
manufacturing network
A manufacturing network is an interconnected system of facilities, suppliers, technologies, and logistics that collaboratively plan, produce, and distribute goods across multiple locations.
-
C.
internet infrastructure component
An internet infrastructure component is a foundational hardware or software element—such as routers, switches, servers, cables, or protocols—that enables the transmission, routing, and reliable delivery of data across interconnected networks.
-
D.
network upgrade initiative
A network upgrade initiative is a coordinated project to enhance an organization’s network infrastructure, capacity, performance, and security to meet current and future business needs.
-
E.
networking hardware company
A networking hardware company designs, manufactures, and sells physical devices and infrastructure that enable data communication and connectivity across computer networks.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:51 p.m.