Triple
T19692290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VaultPress |
E472862
|
entity |
| Predicate | storesBackups |
P63988
|
FINISHED |
| Object | cloud storage |
—
|
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: cloud storage | Statement: [VaultPress, storesBackups, cloud storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesBackups Context triple: [VaultPress, storesBackups, cloud storage]
-
A.
backsUp
Indicates that one entity provides support, reinforcement, or confirmation for another entity’s actions, statements, or position.
-
B.
backupCommander
Indicates that one entity serves as the designated backup or alternate commander for another entity.
-
C.
supportsBackupVaults
Indicates that an entity provides compatibility with or the ability to use backup vaults for storing or managing backups.
-
D.
storesInterfaceIn
Indicates that one entity keeps or maintains an interface definition within another entity (such as a container, module, or storage location).
-
E.
store
chosen
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e64210cddc8190836faa2996a44457 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.