Triple

T8993634
Position Surface form Disambiguated ID Type / Status
Subject GPFS E214846 entity
Predicate supportsScaleProperty P79560 FINISHED
Object petabyte-scale storage 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: petabyte-scale storage | Statement: [GPFS, supportsScaleProperty, petabyte-scale storage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsScaleProperty
Context triple: [GPFS, supportsScaleProperty, petabyte-scale storage]
  • A. hasScale
    Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
  • B. hasScaleHeight
    Indicates the characteristic vertical distance over which a quantity (such as pressure, density, or concentration) decreases by a fixed factor in a stratified medium.
  • C. scalesWith
    Indicates that a change in one quantity is systematically associated with a proportional or otherwise dependent change in another quantity.
  • D. coversScale chosen
    Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
  • E. scalingProperty
    Indicates how a quantity or behavior changes in proportion to changes in another variable, typically under resizing or rescaling conditions.
  • 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_69ca83a05c608190bdfdbdb25e994b39 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc687798a881908e6fdd9a39219f1d completed April 1, 2026, 12:36 a.m.
PD Predicate disambiguation batch_69cc5edba0f88190b97401636a076d7a completed March 31, 2026, 11:55 p.m.
Created at: March 30, 2026, 7:04 p.m.