Triple
T5768070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5766 |
E127261
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 3489
RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
|
E544001
|
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 3489 | Statement: [RFC 5766, obsoletes, RFC 3489]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3489 Context triple: [RFC 5766, obsoletes, RFC 3489]
-
A.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
B.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
C.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols 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 3489 Triple: [RFC 5766, obsoletes, RFC 3489]
Generated description
RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3489 Target entity description: RFC 3489 is an early IETF specification that defined the original STUN protocol for discovering a device’s public IP address and port in NAT traversal scenarios.
-
A.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
B.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
C.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3417
RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
- 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.