Triple
T8210130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FFDHE groups |
E191792
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object | RFC 7919 |
E36660
|
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 7919 | Statement: [FFDHE groups, definedInRFC, RFC 7919]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7919 Context triple: [FFDHE groups, definedInRFC, RFC 7919]
-
A.
RFC 7919
chosen
RFC 7919 is an Internet standard that specifies the use of predefined Diffie–Hellman groups for secure key exchange in TLS and related protocols.
-
B.
RFC 5991
RFC 5991 is an Internet Engineering Task Force (IETF) standards document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve its security and operational behavior.
-
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 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.
-
E.
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.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dd881c8190adcbeb2f33d3295c |
completed | March 31, 2026, 7:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd34b49fb88190b30a89d594ed4ada |
completed | April 1, 2026, 3:07 p.m. |
Created at: March 30, 2026, 5:44 p.m.