Triple

T311052
Position Surface form Disambiguated ID Type / Status
Subject RFC 4253 E7607 entity
Predicate appliesTo P1129 FINISHED
Object SSH-2 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-2 | Statement: [RFC 4253, appliesTo, SSH-2]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SSH-2
Context triple: [RFC 4253, appliesTo, SSH-2]
  • 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. SSH Communications Security
    SSH Communications Security is a Finnish cybersecurity company best known for developing and commercializing the Secure Shell (SSH) protocol and related secure communications solutions.
  • C. RFC 5246
    RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
  • D. 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.
  • E. RFC 2246
    RFC 2246 is the original specification of the Transport Layer Security (TLS) protocol version 1.0, defining the foundational standard for securing communications over computer networks.
  • 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ea49636c8190a69cbd951fc0a4db completed Feb. 28, 2026, 1:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3c417a34c81909b724ecabf38ccb3 completed March 1, 2026, 4:44 a.m.
Created at: Feb. 28, 2026, 1:07 p.m.