Triple
T26892006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scale Space |
E677201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scale-up hub |
C52173
|
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: scale-up hub Context triple: [Scale Space, instanceOf, scale-up hub]
-
A.
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.
-
B.
information and communications technology hub
An information and communications technology hub is a centralized environment—physical, virtual, or hybrid—where ICT infrastructure, services, expertise, and innovation converge to support connectivity, digital operations, and technological development for organizations and communities.
-
C.
healthcare innovation hub
A healthcare innovation hub is a collaborative ecosystem that brings together clinicians, researchers, entrepreneurs, and technologists to develop, test, and scale new solutions that improve health outcomes, patient experience, and system efficiency.
-
D.
energy hub
An energy hub is a centralized system or facility that integrates, converts, stores, and distributes multiple forms of energy (such as electricity, heat, and fuels) to optimize efficiency, reliability, and sustainability across connected users and infrastructures.
-
E.
networking hub
A networking hub is a central device or platform that connects multiple computers or network devices, enabling data exchange and communication among them within a local network.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 5:45 a.m.