Triple
T2002225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poly1305 |
E43495
|
entity |
| Predicate | standardizedIn |
P7508
|
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: [Poly1305, standardizedIn, RFC 8439]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8439 Context triple: [Poly1305, standardizedIn, 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 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.
-
C.
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.
-
D.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
-
E.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8820cec8190a945e5daeb8c9df6 |
completed | March 7, 2026, 5:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae0342ef8c8190b7771076282981c3 |
completed | March 8, 2026, 11:16 p.m. |
Created at: March 4, 2026, 7:37 p.m.