Triple
T5768117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interactive Connectivity Establishment |
E127262
|
entity |
| Predicate | updatedBy |
P1121
|
FINISHED |
| Object |
RFC 8445
RFC 8445 is the IETF specification that modernizes and clarifies the Interactive Connectivity Establishment (ICE) protocol for NAT traversal in real-time communications.
|
E544006
|
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 8445 | Statement: [Interactive Connectivity Establishment, updatedBy, RFC 8445]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8445 Context triple: [Interactive Connectivity Establishment, updatedBy, RFC 8445]
-
A.
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.
-
B.
RFC 4555
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
C.
RFC 8551
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
-
D.
RFC 4844
RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
-
E.
RFC 8728
RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
- 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 8445 Triple: [Interactive Connectivity Establishment, updatedBy, RFC 8445]
Generated description
RFC 8445 is the IETF specification that modernizes and clarifies the Interactive Connectivity Establishment (ICE) protocol for NAT traversal in real-time communications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 8445 Target entity description: RFC 8445 is the IETF specification that modernizes and clarifies the Interactive Connectivity Establishment (ICE) protocol for NAT traversal in real-time communications.
-
A.
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.
-
B.
RFC 4555
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
C.
RFC 8551
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
-
D.
RFC 4844
RFC 4844 is an Internet Engineering Task Force (IETF) document that defines the framework and responsibilities of the RFC Editor function within the RFC Series.
-
E.
RFC 8728
RFC 8728 is an Internet Engineering Task Force (IETF) document that specifies updates and procedures related to the RFC Editor’s role in the publication process of RFCs.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029731adc8190888adc8178a08e90 |
completed | March 22, 2026, 5:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07e61127c8190833e279403af6605 |
completed | March 22, 2026, 11:42 p.m. |
| NEDg | Description generation | batch_69c08cc5c48481909c1ac21d586b3263 |
completed | March 23, 2026, 12:43 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c08d42cac88190b6cd454e8c31a4ef |
completed | March 23, 2026, 12:45 a.m. |
Created at: March 22, 2026, 3:49 p.m.