Triple
T27591507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rook |
E699797
|
entity |
| Predicate | supportsStorageBackend |
P11254
|
FINISHED |
| Object | Ceph |
—
|
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: Ceph | Statement: [Rook, supportsStorageBackend, Ceph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStorageBackend Context triple: [Rook, supportsStorageBackend, Ceph]
-
A.
supportsBlockStorage
Indicates that one entity provides or is compatible with block-level storage capabilities for another entity.
-
B.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
C.
supportsKeyStorage
Indicates that an entity is capable of securely storing cryptographic keys or similar sensitive key material.
-
D.
mayUseStorageType
Indicates that an entity is permitted to use or access a particular type of storage.
-
E.
supportsDatastoreType
chosen
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of datastore.
- 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_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: April 27, 2026, 2:05 p.m.