Triple
T28509854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PowerShell Remoting |
E721451
|
entity |
| Predicate | defaultSecureTransport |
P104463
|
FINISHED |
| Object | HTTPS |
—
|
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: HTTPS | Statement: [PowerShell Remoting, defaultSecureTransport, HTTPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultSecureTransport Context triple: [PowerShell Remoting, defaultSecureTransport, HTTPS]
-
A.
defaultPortSecure
Indicates that the default network port for a service or application is configured to use secure communication (e.g., encrypted or authenticated).
-
B.
securesProtocol
Indicates that one entity protects, safeguards, or enforces the security of a communication or operational protocol for another entity.
-
C.
consideredSecure
Indicates that something is regarded as safe from harm, risk, or unauthorized access according to given criteria or standards.
-
D.
supportsEncryptionInTransit
chosen
Indicates that one entity provides or enables protection of data while it is being transmitted between entities.
-
E.
hasSecureCommunications
Indicates that one entity maintains protected, confidential, and tamper-resistant channels for exchanging information with 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_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 3:11 a.m.