Triple
T11351404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iWARP |
E268846
|
entity |
| Predicate | isSpecifiedIn |
P7659
|
FINISHED |
| Object |
RFC 5047
RFC 5047 is an IETF standard that defines the direct data placement (DDP) and remote direct memory access (RDMA) protocols over TCP/IP for the iWARP architecture.
|
E920321
|
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 5047 | Statement: [iWARP, isSpecifiedIn, RFC 5047]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5047 Context triple: [iWARP, isSpecifiedIn, RFC 5047]
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
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.
-
C.
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.
-
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 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- 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 5047 Triple: [iWARP, isSpecifiedIn, RFC 5047]
Generated description
RFC 5047 is an IETF standard that defines the direct data placement (DDP) and remote direct memory access (RDMA) protocols over TCP/IP for the iWARP architecture.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 5047 Target entity description: RFC 5047 is an IETF standard that defines the direct data placement (DDP) and remote direct memory access (RDMA) protocols over TCP/IP for the iWARP architecture.
-
A.
RFC 4787
RFC 4787 is an IETF standards document that specifies behavioral requirements for network address translation (NAT) devices handling unicast UDP traffic.
-
B.
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.
-
C.
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.
-
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 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea24489081908fbf47fd2e6d709c |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5439a7ee481908d244f79041b3af6 |
completed | April 19, 2026, 9:05 p.m. |
| NEDg | Description generation | batch_69e5474b77948190b2c45831871383e8 |
completed | April 19, 2026, 9:21 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69e54eeba4a88190af128a99c277853a |
completed | April 19, 2026, 9:53 p.m. |
Created at: April 8, 2026, 9:33 p.m.