Triple
T27588922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manila API |
E699748
|
entity |
| Predicate | supportsBackendType |
P24486
|
FINISHED |
| Object | vendor-specific storage drivers |
—
|
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: vendor-specific storage drivers | Statement: [Manila API, supportsBackendType, vendor-specific storage drivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBackendType Context triple: [Manila API, supportsBackendType, vendor-specific storage drivers]
-
A.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
C.
supportsRenderingBackend
Indicates that one entity is capable of using or working with a specified rendering backend to perform rendering operations.
-
D.
supportsPluginType
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of plugin.
-
E.
hasBackend
Indicates that one entity functions as the backend or server-side component that supports or powers 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_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 27, 2026, 2:05 p.m.