Triple
T36872855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ssh-keysign |
E911266
|
entity |
| Predicate | readsHostKeysFrom |
P43634
|
FINISHED |
| Object | /etc/ssh/ssh_host_rsa_key |
—
|
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: /etc/ssh/ssh_host_rsa_key | Statement: [ssh-keysign, readsHostKeysFrom, /etc/ssh/ssh_host_rsa_key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: readsHostKeysFrom Context triple: [ssh-keysign, readsHostKeysFrom, /etc/ssh/ssh_host_rsa_key]
-
A.
isAKeyHostFor
Indicates that one entity serves as a primary or essential host required for the life cycle, survival, or functioning of another entity.
-
B.
readsFrom
chosen
Indicates that one entity obtains or accesses data, information, or content from another entity as a source.
-
C.
readsInto
Indicates that one entity reads or interprets information from another entity as input or source content.
-
D.
keyImport
Indicates the action or process of bringing an existing cryptographic key into a system or application for use.
-
E.
readIn
Indicates that an entity reads or studies something within a particular location or context.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.