Triple
T27589822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStack Magnum |
E699766
|
entity |
| Predicate | supportsClusterType |
P24486
|
FINISHED |
| Object | Kubernetes cluster |
—
|
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: Kubernetes cluster | Statement: [OpenStack Magnum, supportsClusterType, Kubernetes cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsClusterType Context triple: [OpenStack Magnum, supportsClusterType, Kubernetes cluster]
-
A.
supportsClusterManagement
Indicates that one entity provides functionality or resources that enable the management and coordination of a cluster of related entities.
-
B.
typeOfCluster
Indicates that one entity is classified as a specific kind or category of cluster in relation to another entity.
-
C.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
-
D.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
E.
hasCluster
Indicates that one entity possesses, contains, or is associated with a specific cluster or grouping of related elements.
- 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_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: April 27, 2026, 2:05 p.m.