Triple

T9311921
Position Surface form Disambiguated ID Type / Status
Subject ChaCha20 E224025 entity
Predicate specifiedIn P775 FINISHED
Object RFC 8439 E50666 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: RFC 8439 | Statement: [ChaCha20, specifiedIn, RFC 8439]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 8439
Context triple: [ChaCha20, specifiedIn, RFC 8439]
  • A. RFC 8439 chosen
    RFC 8439 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code, defining the ChaCha20-Poly1305 AEAD construction widely used in modern cryptographic protocols.
  • B. RFC 8729
    RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
  • C. RFC 8996
    RFC 8996 is an Internet Engineering Task Force (IETF) standard that formally deprecates the use of older Transport Layer Security (TLS) protocol versions in favor of more secure modern alternatives.
  • D. RFC 7539
    RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
  • E. RFC 9293
    RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
  • 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_69ca8425f4fc81909c1c586e9a5b7530 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd20ae96e481909a1af9ea1c91f2b2 completed April 1, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0e39d03508190aca18600c33bfdd8 completed April 4, 2026, 10:10 a.m.
Created at: March 30, 2026, 7:37 p.m.