Triple

T1836224
Position Surface form Disambiguated ID Type / Status
Subject RFC 8332 E41072 entity
Predicate keyType P21838 FINISHED
Object RSA E5909 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: RSA | Statement: [RFC 8332, keyType, RSA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RSA
Context triple: [RFC 8332, keyType, RSA]
  • A. RSA chosen
    RSA is a widely used public-key cryptographic algorithm that enables secure key exchange and digital signatures in many internet security protocols.
  • B. RSA Security
    RSA Security is a pioneering American cybersecurity company best known for its contributions to public-key cryptography and secure data encryption technologies.
  • C. RSA Fellowship
    The RSA Fellowship is a global community of accomplished individuals from diverse fields who collaborate to address social challenges and promote innovative solutions for the public good.
  • 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. ElGamal
    ElGamal is a public-key cryptosystem based on the discrete logarithm problem, widely used for secure encryption and digital signatures in various cryptographic protocols.
  • 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_69a88647f9388190909bc36e795bdaec completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb028226481908558c11449e1d6b6 completed March 7, 2026, 4:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69adc9b6dc9481908a83e60aee326bc4 completed March 8, 2026, 7:10 p.m.
Created at: March 4, 2026, 7:33 p.m.