Triple
T13410499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugaku |
E320072
|
entity |
| Predicate | peakPerformanceRmax |
P50940
|
FINISHED |
| Object | 442 PFLOPS |
—
|
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: 442 PFLOPS | Statement: [Fugaku, peakPerformanceRmax, 442 PFLOPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPerformanceRmax Context triple: [Fugaku, peakPerformanceRmax, 442 PFLOPS]
-
A.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
B.
peakRating
chosen
Indicates the highest rating value that has been achieved or recorded for an entity over a given period or context.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
maximumEfficiency
Indicates that an entity operates at its highest possible level of performance or productivity under given conditions.
-
E.
peakPerformanceUnit
Indicates a unit or component that operates at or is responsible for achieving peak or maximum performance within a system or process.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb3facc819088c1af3b59237e7a |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:35 p.m.