Triple
T10623788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2026 |
E250269
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 8179
RFC 8179 is an IETF document that updates and clarifies the intellectual property rights (IPR) policies and procedures governing contributions to IETF standards.
|
E876213
|
NE FINISHED |
How this triple was built (4 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 8179 | Statement: [RFC 2026, obsoletedBy, RFC 8179]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8179 Context triple: [RFC 2026, obsoletedBy, RFC 8179]
-
A.
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.
-
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 8439
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.
-
D.
RFC 8310
RFC 8310 is an IETF standard that specifies the use of Transport Layer Security (TLS) to provide privacy and integrity for DNS queries and responses.
-
E.
RFC 6189
RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 8179 Triple: [RFC 2026, obsoletedBy, RFC 8179]
Generated description
RFC 8179 is an IETF document that updates and clarifies the intellectual property rights (IPR) policies and procedures governing contributions to IETF standards.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8179 Target entity description: RFC 8179 is an IETF document that updates and clarifies the intellectual property rights (IPR) policies and procedures governing contributions to IETF standards.
-
A.
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.
-
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 8439
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.
-
D.
RFC 8310
RFC 8310 is an IETF standard that specifies the use of Transport Layer Security (TLS) to provide privacy and integrity for DNS queries and responses.
-
E.
RFC 6189
RFC 6189 is the Internet Engineering Task Force (IETF) standard that defines the ZRTP protocol for secure key agreement in Voice over IP communications.
- F. None of above. chosen
Provenance (5 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7f11fc8190aed858f2e1443c08 |
completed | April 8, 2026, 11:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d96b9a27f881908e451bfa6c118af4 |
completed | April 10, 2026, 9:28 p.m. |
| NEDg | Description generation | batch_69d96fe942648190a8779e13e16b9196 |
completed | April 10, 2026, 9:47 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d970f3f78081909bcb2dae6dae06d5 |
completed | April 10, 2026, 9:51 p.m. |
Created at: April 8, 2026, 8:52 p.m.