Triple

T63752
Position Surface form Disambiguated ID Type / Status
Subject SSH E1267 entity
Predicate abbreviationOf P590 FINISHED
Object Secure Shell 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: Secure Shell | Statement: [SSH, abbreviationOf, Secure Shell]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Secure Shell
Context triple: [SSH, abbreviationOf, Secure Shell]
  • 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. 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.
  • C. TLS
    TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
  • D. Telnet
    Telnet is a network protocol and command-line tool that allows users to remotely access and manage devices over a text-based terminal connection.
  • E. Wired Equivalent Privacy
    Wired Equivalent Privacy (WEP) is an early and now largely obsolete Wi‑Fi security protocol known for its weak encryption and significant vulnerabilities.
  • 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_69a25679e0688190bc0360314af3ef46 completed Feb. 28, 2026, 2:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69a25ab9477881908508e3130068bca3 completed Feb. 28, 2026, 3:02 a.m.
Created at: Feb. 28, 2026, 2:02 a.m.