Triple
T28509853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerShell Remoting |
E721451
|
entity |
| Predicate | defaultTransport |
P175205
|
FINISHED |
| Object | HTTP |
—
|
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: HTTP | Statement: [PowerShell Remoting, defaultTransport, HTTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultTransport Context triple: [PowerShell Remoting, defaultTransport, HTTP]
-
A.
usesTransport
Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
-
B.
defaultDriver
Indicates that one entity is designated as the primary or standard driver for another entity (such as a vehicle or account).
-
C.
definesTransportFor
chosen
Indicates that one entity specifies or determines the means, method, or system of transport used by another entity.
-
D.
assumesTransport
Indicates that one entity takes responsibility for carrying or conveying another entity from one place to another.
-
E.
isTransport
Indicates that one entity serves as a means or method for conveying or carrying another entity from one place to another.
- 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_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 3:11 a.m.