Triple
T8009064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6410 |
E186437
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 5657
RFC 5657 is an Internet Engineering Task Force (IETF) document that provided guidelines related to the standards process before being superseded by RFC 6410.
|
E707269
|
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 5657 | Statement: [RFC 6410, obsoletes, RFC 5657]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5657 Context triple: [RFC 6410, obsoletes, RFC 5657]
-
A.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
B.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
-
C.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
D.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
E.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
- 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 5657 Triple: [RFC 6410, obsoletes, RFC 5657]
Generated description
RFC 5657 is an Internet Engineering Task Force (IETF) document that provided guidelines related to the standards process before being superseded by RFC 6410.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 5657 Target entity description: RFC 5657 is an Internet Engineering Task Force (IETF) document that provided guidelines related to the standards process before being superseded by RFC 6410.
-
A.
RFC 6557
RFC 6557 is an Internet Engineering Task Force (IETF) document that defines procedures and guidelines for the maintenance and distribution of the IANA time zone database.
-
B.
RFC 6587
RFC 6587 is an IETF standard that specifies the message framing and transmission of syslog messages over TCP.
-
C.
RFC 5764
RFC 5764 is an IETF standard that defines how to use Datagram Transport Layer Security (DTLS) to secure media streams in the Secure Real-time Transport Protocol (SRTP) for applications like VoIP and video conferencing.
-
D.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
E.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3d6f76408190a1312369521a187a |
completed | March 31, 2026, 3:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc569e90d48190a1bf1495496017f8 |
completed | March 31, 2026, 11:19 p.m. |
| NEDg | Description generation | batch_69cc58a8f3d08190bec84dc1ba3b5b84 |
completed | March 31, 2026, 11:28 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cc5cb791b48190bd5004b518d23f84 |
completed | March 31, 2026, 11:45 p.m. |
Created at: March 30, 2026, 5:19 p.m.