Triple
T28618410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remote Desktop Gateway |
E724323
|
entity |
| Predicate | tunnelsProtocolOver |
P163116
|
FINISHED |
| Object | RDP over 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: RDP over HTTPS | Statement: [Remote Desktop Gateway, tunnelsProtocolOver, RDP over HTTPS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tunnelsProtocolOver Context triple: [Remote Desktop Gateway, tunnelsProtocolOver, RDP over HTTPS]
-
A.
tunnelsProtocol
chosen
Indicates that one communication protocol is encapsulated and transmitted within another protocol, creating a tunnel through the outer protocol’s channel.
-
B.
tunnelType
Indicates the specific kind or classification of a tunnel associated with an entity.
-
C.
tunnelUse
Indicates that one entity makes use of or passes through a tunnel associated with another entity.
-
D.
tunnels
Indicates that one entity passes through, under, or within another entity via a tunnel-like passage or structure.
-
E.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.