Triple

T63783
Position Surface form Disambiguated ID Type / Status
Subject SSH E1267 entity
Predicate hasVersion P455 FINISHED
Object SSH-1 E1267 NE 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: SSH-1 | Statement: [SSH, hasVersion, SSH-1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SSH-1
Context triple: [SSH, hasVersion, SSH-1]
  • A. SSH chosen
    SSH (Secure Shell) is a cryptographic network protocol used to securely access, manage, and transfer data between remote computers over unsecured networks.
  • B. Dropbear SSH
    Dropbear SSH is a lightweight, open-source SSH server and client implementation designed for embedded systems and resource-constrained environments.
  • C. Diffie–Hellman key exchange
    Diffie–Hellman key exchange is a foundational cryptographic protocol that enables two parties to securely establish a shared secret over an insecure communication channel.
  • D. SSL 3.0
    SSL 3.0 is an obsolete cryptographic protocol that once secured internet communications and served as the foundation for the early versions of TLS.
  • E. PuTTY
    PuTTY is a widely used free and open-source terminal emulator and network client for Windows and other platforms, supporting protocols like SSH, Telnet, and serial connections.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a24ba4f760819081f6638a3c70538a completed Feb. 28, 2026, 1:57 a.m.
NER Named-entity recognition batch_69a24ee576fc8190b42e5d50767beefb completed Feb. 28, 2026, 2:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69a262406a6c81909be211fb2418ccbb completed Feb. 28, 2026, 3:34 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.