Triple

T36828414
Position Surface form Disambiguated ID Type / Status
Subject Sierra E910070 entity
Predicate LINPACKPerformanceUnit P186561 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: [Sierra, LINPACKPerformanceUnit, petaflops]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: LINPACKPerformanceUnit
Context triple: [Sierra, LINPACKPerformanceUnit, petaflops]
  • A. LINPACKPerformance
    Indicates the level of computational performance achieved by an entity when running the LINPACK benchmark, typically measured in floating-point operations per second.
  • B. floatingPointPerformance
    Indicates the level of computational capability or efficiency an entity has when performing floating-point arithmetic operations.
  • C. gpuComputePerformance
    Indicates the level of processing capability a GPU can deliver for computational tasks, typically measured in operations per unit time.
  • D. benchmarkFamily
    Indicates that one entity serves as a benchmark or reference standard for evaluating or comparing another entity within the same family or category.
  • E. benchmarkVariant
    Indicates that one entity is a specific version or variation of another entity used for benchmarking or performance comparison.
  • F. None of above. chosen

Provenance (4 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_69f9fe1a1ca4819084c196f0041f0be2 completed May 5, 2026, 2:26 p.m.
PD Predicate disambiguation batch_69f7cf7890008190a8bc355ff2d61c86 completed May 3, 2026, 10:43 p.m.
PDg Predicate description generation batch_69f9fd66eed48190bdc26a8def328c2d completed May 5, 2026, 2:23 p.m.
Created at: May 3, 2026, 4:13 p.m.