Triple
T36872751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ssh-agent |
E911264
|
entity |
| Predicate | acceptsCommand |
P11061
|
FINISHED |
| Object | ssh-add |
—
|
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: ssh-add | Statement: [ssh-agent, acceptsCommand, ssh-add]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsCommand Context triple: [ssh-agent, acceptsCommand, ssh-add]
-
A.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
B.
hasCommand
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
-
C.
supportsCommand
chosen
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
D.
hasCommandResponsibilityFor
Indicates that one entity holds authoritative control over, and is responsible for directing and overseeing, the actions or operations of another entity.
-
E.
commandReceived
Indicates that an entity has successfully received a command issued by another entity or system.
- 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.