Triple

T22197372
Position Surface form Disambiguated ID Type / Status
Subject RFC 9147 E548582 entity
Predicate obsoletes P101 FINISHED
Object RFC 6347
RFC 6347 is the IETF specification that originally defined the Datagram Transport Layer Security (DTLS) protocol, providing TLS-equivalent security over datagram-based transports such as UDP.
 E544000 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 6347 | Statement: [RFC 9147, obsoletes, RFC 6347]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 6347
Context triple: [RFC 9147, obsoletes, RFC 6347]
  • A. RFC 6347
    RFC 6347 is the Internet Engineering Task Force (IETF) standard that specifies Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over datagram-based transports such as UDP.
  • B. RFC 6147
    RFC 6147 is an IETF standard that specifies DNS64, a mechanism for synthesizing IPv6 addresses from IPv4 DNS records to enable IPv6-only hosts to communicate with IPv4 servers.
  • C. RFC 6047
    RFC 6047 is an Internet standards document that specifies how iCalendar scheduling messages are transported via email using the iMIP protocol.
  • D. RFC 6437
    RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
  • E. RFC 4347
    RFC 4347 is the Internet Engineering Task Force (IETF) specification that introduces Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over unreliable datagram transports such as UDP.
  • 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 6347
Triple: [RFC 9147, obsoletes, RFC 6347]
Generated description
RFC 6347 is the IETF specification that originally defined the Datagram Transport Layer Security (DTLS) protocol, providing TLS-equivalent security over datagram-based transports such as UDP.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: RFC 6347
Target entity description: RFC 6347 is the IETF specification that originally defined the Datagram Transport Layer Security (DTLS) protocol, providing TLS-equivalent security over datagram-based transports such as UDP.
  • A. RFC 6347 chosen
    RFC 6347 is the Internet Engineering Task Force (IETF) standard that specifies Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over datagram-based transports such as UDP.
  • B. RFC 6147
    RFC 6147 is an IETF standard that specifies DNS64, a mechanism for synthesizing IPv6 addresses from IPv4 DNS records to enable IPv6-only hosts to communicate with IPv4 servers.
  • C. RFC 6047
    RFC 6047 is an Internet standards document that specifies how iCalendar scheduling messages are transported via email using the iMIP protocol.
  • D. RFC 6437
    RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
  • E. RFC 4347
    RFC 4347 is the Internet Engineering Task Force (IETF) specification that introduces Datagram Transport Layer Security (DTLS), a protocol providing TLS-like security over unreliable datagram transports such as UDP.
  • F. None of above.

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_69e11e3ecc7c8190b5f94cd8f42e9d37 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12ae8c74c819080c7f9e8383ecaa7 completed April 28, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0aa612ee34819086a5af4bdb3676df completed May 18, 2026, 5:39 a.m.
NEDg Description generation batch_6a0aa6b04798819088ab3ed8c3fe53af completed May 18, 2026, 5:42 a.m.
NED2 Entity disambiguation (via description) batch_6a0aa72467d4819093f84573de7c8da2 completed May 18, 2026, 5:44 a.m.
Created at: April 16, 2026, 8:36 p.m.