Triple
T27589989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenStack Zaqar |
E699769
|
entity |
| Predicate | canUseBackend |
P9928
|
FINISHED |
| Object | MongoDB |
—
|
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: MongoDB | Statement: [OpenStack Zaqar, canUseBackend, MongoDB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseBackend Context triple: [OpenStack Zaqar, canUseBackend, MongoDB]
-
A.
hasBackend
Indicates that one entity functions as the backend or server-side component that supports or powers another entity.
-
B.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
D.
canBeRunBehind
Indicates that one entity is capable of being executed or operated in a secondary or background position relative to another entity.
-
E.
supportsRenderingBackend
Indicates that one entity is capable of using or working with a specified rendering backend to perform rendering operations.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:05 p.m.