Triple
T19403051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier |
E485376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | exascale 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 computer Context triple: [Frontier, instanceOf, exascale 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.
supercomputer manufacturer
A supercomputer manufacturer is a company that designs, builds, and delivers ultra-high-performance computing systems optimized for large-scale scientific, engineering, and data-intensive applications.
-
D.
high-performance computing centre
A high-performance computing centre is a specialized facility that provides advanced computational resources, high-speed networking, and expert support to enable large-scale, data-intensive, and complex scientific, engineering, and industrial computations.
-
E.
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.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:36 p.m.