Triple
T7938166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStack Glance |
E184331
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | OpenStack Horizon |
E184333
|
NE 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 Horizon | Statement: [OpenStack Glance, usedBy, OpenStack Horizon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenStack Horizon Context triple: [OpenStack Glance, usedBy, OpenStack Horizon]
-
A.
OpenStack Horizon
chosen
OpenStack Horizon is the web-based dashboard for managing and monitoring OpenStack cloud resources through a graphical user interface.
-
B.
OpenStack
OpenStack is an open-source cloud computing platform that provides a suite of software tools for building and managing public and private clouds.
-
C.
OpenStack Congress
OpenStack Congress is a governance and policy-as-a-service component of the OpenStack cloud platform that enables centralized policy enforcement across diverse cloud services.
-
D.
OpenStack Keystone
OpenStack Keystone is the identity service component of the OpenStack cloud platform, providing authentication, authorization, and service catalog capabilities.
-
E.
OpenStack Inspector
OpenStack Inspector is a hardware introspection service in the OpenStack ecosystem that collects and analyzes bare metal node data to support automated provisioning and management.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc564a4fac8190972f9dfa7c026ea8 |
completed | March 31, 2026, 11:18 p.m. |
Created at: March 30, 2026, 5:08 p.m.