Triple
T28509875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerShell Remoting |
E721451
|
entity |
| Predicate | runsOverPort |
P164602
|
FINISHED |
| Object | 5985 |
—
|
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: 5985 | Statement: [PowerShell Remoting, runsOverPort, 5985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsOverPort Context triple: [PowerShell Remoting, runsOverPort, 5985]
-
A.
runsDirectlyOver
Indicates that one entity passes or extends immediately above another along its length or span, without significant vertical separation or intervening structures.
-
B.
blowsOver
Indicates that one entity is toppled or knocked down by the force or movement of another entity.
-
C.
runsInto
Indicates that one entity moves so as to collide or come into sudden contact with another entity.
-
D.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
E.
canRunOver
Indicates that one entity has the ability or potential to move across or pass over another entity, typically in a way that could cause impact or damage.
- F. None of above. chosen
Provenance (4 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_69f64f7388a88190a80dc4730f92eded |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:11 a.m.