Triple
T3806528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier |
E93020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | exascale supercomputer |
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 supercomputer Context triple: [Frontier, instanceOf, exascale supercomputer]
-
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 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.
-
D.
VMEbus system
A VMEbus system is a modular computer architecture that uses a shared parallel bus to interconnect processors, memory, and I/O boards in a standardized backplane for industrial and embedded applications.
-
E.
particle accelerator complex
A particle accelerator complex is an integrated facility comprising accelerators, beamlines, detectors, and support infrastructure designed to accelerate charged particles to high energies for research, medical, or industrial applications.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:16 p.m.