Triple

T27589847
Position Surface form Disambiguated ID Type / Status
Subject OpenStack Magnum E699766 entity
Predicate supportsClusterUpgrade P117866 FINISHED
Object true 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: true | Statement: [OpenStack Magnum, supportsClusterUpgrade, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsClusterUpgrade
Context triple: [OpenStack Magnum, supportsClusterUpgrade, true]
  • A. supportsClusterManagement
    Indicates that one entity provides functionality or resources that enable the management and coordination of a cluster of related entities.
  • B. supportsMigrationOf
    Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
  • C. supportsUpgrade chosen
    Indicates that one entity is capable of accepting, enabling, or being compatible with an upgrade provided by another entity.
  • D. isOldCluster
    Indicates that a given cluster has existed for a long time or has reached an advanced age relative to other clusters.
  • E. supportsSinceVersion
    Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
  • 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_69ef6a4d71f081909a1235763206b691 completed April 27, 2026, 1:53 p.m.
NER Named-entity recognition batch_69ff41645c548190b7cb4e53079b93ef completed May 9, 2026, 2:15 p.m.
PD Predicate disambiguation batch_69ff410aa33c8190869ba769ac2a93ce completed May 9, 2026, 2:13 p.m.
Created at: April 27, 2026, 2:05 p.m.