Triple

T27589804
Position Surface form Disambiguated ID Type / Status
Subject OpenStack Magnum E699766 entity
Predicate supportsOrchestrationEngine P58238 FINISHED
Object Kubernetes NE NERFINISHED

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 | Statement: [OpenStack Magnum, supportsOrchestrationEngine, Kubernetes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsOrchestrationEngine
Context triple: [OpenStack Magnum, supportsOrchestrationEngine, Kubernetes]
  • A. supportsOrchestrator chosen
    Indicates that one entity provides the necessary capabilities or compatibility for another entity to function as an orchestrator within a coordinated system or workflow.
  • B. hasOrchestration
    Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
  • C. usesOrchestration
    Indicates that one entity employs orchestration mechanisms or tools to coordinate, manage, or automate the behavior and interactions of other entities or processes.
  • D. helpsOrchestrate
    Indicates involvement in coordinating, organizing, or managing the execution of an activity or process, often in collaboration with others.
  • E. supportsOperationsIn
    Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
  • 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_69ff370698ec81909bb1596d7d4112ba completed May 9, 2026, 1:30 p.m.
PD Predicate disambiguation batch_69ff3699b6288190b564839cb05f5cf6 completed May 9, 2026, 1:28 p.m.
Created at: April 27, 2026, 2:05 p.m.