Triple

T36828465
Position Surface form Disambiguated ID Type / Status
Subject BlueGene/L E910071 entity
Predicate linpackPerformance P61344 FINISHED
Object 280.6 teraflops 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: 280.6 teraflops | Statement: [BlueGene/L, linpackPerformance, 280.6 teraflops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: linpackPerformance
Context triple: [BlueGene/L, linpackPerformance, 280.6 teraflops]
  • A. LINPACKPerformanceUnit
    Indicates the unit of measurement used to express LINPACK benchmark performance results.
  • B. LINPACKPerformance chosen
    Indicates the level of computational performance achieved by an entity when running the LINPACK benchmark, typically measured in floating-point operations per second.
  • C. floatingPointPerformance
    Indicates the level of computational capability or efficiency an entity has when performing floating-point arithmetic operations.
  • D. isForPerformanceIn
    Indicates that something (such as an item, space, or arrangement) is intended to be used in or associated with a particular performance event.
  • E. gpuComputePerformance
    Indicates the level of processing capability a GPU can deliver for computational tasks, typically measured in operations per unit time.
  • 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_69f76e7e9d60819092442fba73290a46 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fa0a7b00948190a257273d9968c5d7 completed May 5, 2026, 3:19 p.m.
PD Predicate disambiguation batch_69f9fec9c9488190ae2a349651a02782 completed May 5, 2026, 2:29 p.m.
Created at: May 3, 2026, 4:13 p.m.