Triple

T7938333
Position Surface form Disambiguated ID Type / Status
Subject OpenStack Horizon E184333 entity
Predicate supportsReleaseModel P19968 FINISHED
Object OpenStack coordinated release cycle 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: OpenStack coordinated release cycle | Statement: [OpenStack Horizon, supportsReleaseModel, OpenStack coordinated release cycle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsReleaseModel
Context triple: [OpenStack Horizon, supportsReleaseModel, OpenStack coordinated release cycle]
  • A. hasReleaseModel chosen
    Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
  • B. supportsContributionModel
    Indicates that one entity enables or is compatible with a particular model or framework for making contributions (such as donations, content, or resources).
  • C. supportsModelType
    Indicates that an entity is compatible with, or can operate using, a specified model type.
  • D. supportsModelVariant
    Indicates that one entity is capable of operating with, being compatible with, or otherwise accommodating a specific variant of a model.
  • E. supportsModelFamily
    Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or use of a particular model family.
  • 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_69ca8290c21c8190906a5ca6fe2b03c4 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3af0a2048190838d1aeda59fda0b completed March 31, 2026, 3:09 a.m.
PD Predicate disambiguation batch_69cae93526d081909303265bf60419fd completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 5:08 p.m.