Triple
T29685619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth Simulator 2 |
E751074
|
entity |
| Predicate | peakPerformanceTFLOPS |
P88583
|
FINISHED |
| Object | 1310 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 1310 | Statement: [Earth Simulator 2, peakPerformanceTFLOPS, 1310]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPerformanceTFLOPS Context triple: [Earth Simulator 2, peakPerformanceTFLOPS, 1310]
-
A.
floatingPointPerformance
chosen
Indicates the level of computational capability or efficiency an entity has when performing floating-point arithmetic operations.
-
B.
neuralEnginePerformance
Indicates the level or efficiency of processing capability provided by a neural engine in performing AI or machine-learning tasks.
-
C.
gpuComputePerformance
Indicates the level of processing capability a GPU can deliver for computational tasks, typically measured in operations per unit time.
-
D.
performanceCores
Indicates a relationship where certain cores within a processor are designated as high-performance cores optimized for speed and intensive tasks.
-
E.
LINPACKPerformance
Indicates the level of computational performance achieved by an entity when running the LINPACK benchmark, typically measured in floating-point operations per second.
- F. None of above.
Provenance (3 batches)
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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67290186481908e59be35101a1817 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:13 p.m.