Triple
T28509852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerShell Remoting |
E721451
|
entity |
| Predicate | usesImplementation |
P16806
|
FINISHED |
| Object | WinRM |
—
|
NE NERFINISHED |
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: WinRM | Statement: [PowerShell Remoting, usesImplementation, WinRM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesImplementation Context triple: [PowerShell Remoting, usesImplementation, WinRM]
-
A.
usesImplement
chosen
Indicates that one entity employs or makes use of another entity as a tool, instrument, or means to perform an action or achieve a purpose.
-
B.
isImplementationOf
Indicates that one entity realizes, fulfills, or concretely carries out the specification, interface, or abstract definition provided by another entity.
-
C.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
-
D.
alsoImplements
Indicates that an entity, in addition to its primary implementation, implements another interface, protocol, or specification as well.
-
E.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 3:11 a.m.