Triple
T36654203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secure Shell (SSH) Connection Protocol |
E904946
|
entity |
| Predicate | multiplexesOver |
P164461
|
FINISHED |
| Object | single encrypted transport |
—
|
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: single encrypted transport | Statement: [Secure Shell (SSH) Connection Protocol, multiplexesOver, single encrypted transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: multiplexesOver Context triple: [Secure Shell (SSH) Connection Protocol, multiplexesOver, single encrypted transport]
-
A.
multiplexes
chosen
Indicates that one entity combines multiple input signals or data streams into a single channel or medium for transmission or processing.
-
B.
multiplexType
Indicates the specific kind or category of multiplex relationship or connection that exists between entities.
-
C.
hasMultiplex
Indicates that one entity possesses or is associated with multiple instances or channels of another entity within a shared structure or system.
-
D.
multiplexing
Indicates combining multiple signals or data streams into a single channel or medium for transmission or processing.
-
E.
multipleAccess
Indicates that an entity can be accessed or used by more than one agent, user, or process, either simultaneously or sequentially.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.