Triple
T13410482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugaku |
E320072
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | exascale-class computer |
C12874
|
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: exascale-class computer Context triple: [Fugaku, instanceOf, exascale-class computer]
-
A.
petascale supercomputer
A petascale supercomputer is a massively parallel high-performance computing system capable of performing at least one quadrillion (10^15) floating-point operations per second, used for large-scale scientific, engineering, and data-intensive simulations.
-
B.
high-performance computing system
chosen
A high-performance computing system is an integrated collection of powerful processors, high-speed interconnects, and optimized software designed to perform large-scale, complex computations at very high speeds.
-
C.
mainframe computer
A mainframe computer is a large, powerful, and highly reliable central computer system designed to process vast amounts of data and support numerous simultaneous users and critical applications, typically used by large organizations.
-
D.
mainframe computer series
A mainframe computer series is a family of high-performance, large-scale computers designed for reliable, centralized processing of massive workloads and critical enterprise applications over multiple generations.
-
E.
InfiniBand interconnect generation
InfiniBand interconnect generation represents the process and configuration logic for creating, parameterizing, and managing high-speed InfiniBand fabric topologies and their associated connectivity resources.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:35 p.m.