Triple
T36872747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ssh-agent |
E911264
|
entity |
| Predicate | doesNotStoreKeys |
P31950
|
FINISHED |
| Object | on disk in decrypted form |
—
|
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: on disk in decrypted form | Statement: [ssh-agent, doesNotStoreKeys, on disk in decrypted form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotStoreKeys Context triple: [ssh-agent, doesNotStoreKeys, on disk in decrypted form]
-
A.
supportsKeyStorage
Indicates that an entity is capable of securely storing cryptographic keys or similar sensitive key material.
-
B.
storesKeys
chosen
Indicates that one entity holds or retains the keys belonging to or used by another entity.
-
C.
isKeyDependent
Indicates that one entity’s existence, validity, or identification depends on another entity’s key or primary identifier.
-
D.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
E.
keySpace
Indicates the logical namespace or partition within a data store or system in which a particular key or set of keys is defined and managed.
- 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_69f76e82339881909607a65c0503d941 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.