Triple
T15267351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cray XK7 |
E364932
|
entity |
| Predicate | peakPerformanceClass |
P51866
|
FINISHED |
| Object | petaflops |
—
|
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: petaflops | Statement: [Cray XK7, peakPerformanceClass, petaflops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPerformanceClass Context triple: [Cray XK7, peakPerformanceClass, petaflops]
-
A.
performanceClass
chosen
Indicates the category or level of performance to which an entity is assigned, typically reflecting its capabilities or quality tier.
-
B.
peakPerformanceRpeak
Indicates the point or condition at which an R-peak (in a signal such as an ECG) reaches its maximum or optimal performance level.
-
C.
peakPerformanceUnit
Indicates a unit or component that operates at or is responsible for achieving peak or maximum performance within a system or process.
-
D.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
E.
performanceWith
Indicates a relationship where two or more entities participate together in the same performance or staged presentation.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0094ca9ac8190a1f97a7b74c96cd5 |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.