Triple
T28509863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerShell Remoting |
E721451
|
entity |
| Predicate | usesCmdlet |
P11061
|
FINISHED |
| Object | Enter-PSSession |
—
|
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: Enter-PSSession | Statement: [PowerShell Remoting, usesCmdlet, Enter-PSSession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCmdlet Context triple: [PowerShell Remoting, usesCmdlet, Enter-PSSession]
-
A.
cmdlet
Indicates a relationship where an entity is a small, specialized command or function used to perform a specific operation within a command-line or scripting environment.
-
B.
disabledByCmdlet
Indicates that something is rendered disabled or inactive as a direct result of executing a specific cmdlet.
-
C.
supportsCommand
chosen
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
D.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
E.
usesDirective
Indicates that one entity applies, references, or relies on a specific directive issued or defined by another entity.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 3:11 a.m.