Triple

T10682066
Position Surface form Disambiguated ID Type / Status
Subject AEAD_CHACHA20_POLY1305 E251780 entity
Predicate usedIn P98 FINISHED
Object libsodium E224033 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: libsodium | Statement: [AEAD_CHACHA20_POLY1305, usedIn, libsodium]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: libsodium
Context triple: [AEAD_CHACHA20_POLY1305, usedIn, libsodium]
  • A. libsodium chosen
    libsodium is a modern, easy-to-use, cross-platform cryptographic library that provides high-level APIs for encryption, authentication, and related security operations.
  • B. BoringSSL
    BoringSSL is a Google-maintained fork of OpenSSL focused on security, simplicity, and suitability for large-scale, internal use in projects like Chrome and Android.
  • C. LibreSSL
    LibreSSL is an open-source cryptographic library and SSL/TLS toolkit, forked from OpenSSL by the OpenBSD project to improve code quality and security.
  • D. secp256k1
    secp256k1 is a widely used elliptic curve defined over a 256-bit prime field, best known as the cryptographic foundation for Bitcoin and several other blockchain systems.
  • E. XSalsa20-Poly1305
    XSalsa20-Poly1305 is an authenticated encryption scheme that combines the XSalsa20 stream cipher with the Poly1305 message authentication code to provide both confidentiality and integrity for messages.
  • 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_69d6aa5bd7c08190a816e733b4045c23 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fcc30be481909922844b539b622d completed April 9, 2026, 1:11 a.m.
NED1 Entity disambiguation (via context triple) batch_69d98885abf88190b54ed9db779d3ff0 completed April 10, 2026, 11:32 p.m.
Created at: April 8, 2026, 9:10 p.m.