Triple
T7938150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStack Cinder |
E184330
|
entity |
| Predicate | hasReleaseCadence |
P49318
|
FINISHED |
| Object | aligned with OpenStack releases |
—
|
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: aligned with OpenStack releases | Statement: [OpenStack Cinder, hasReleaseCadence, aligned with OpenStack releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseCadence Context triple: [OpenStack Cinder, hasReleaseCadence, aligned with OpenStack releases]
-
A.
standardReleaseCadence
Indicates a relationship where an entity follows a regular, predefined schedule or frequency for releasing updates or versions.
-
B.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
C.
releaseCadence
chosen
Indicates how frequently and on what schedule something is released or made available.
-
D.
hasReleaseBranch
Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
-
E.
hasReleaseModel
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
- 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.