Triple
T14790010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iMIP |
E347627
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object |
RFC 6047
RFC 6047 is an Internet standards document that specifies how iCalendar scheduling messages are transported via email using the iMIP protocol.
|
E1120154
|
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 6047 | Statement: [iMIP, definedIn, RFC 6047]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6047 Context triple: [iMIP, definedIn, RFC 6047]
-
A.
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.
-
B.
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.
-
C.
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.
-
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 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.
- 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 6047 Triple: [iMIP, definedIn, RFC 6047]
Generated description
RFC 6047 is an Internet standards document that specifies how iCalendar scheduling messages are transported via email using the iMIP protocol.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 6047 Target entity description: RFC 6047 is an Internet standards document that specifies how iCalendar scheduling messages are transported via email using the iMIP protocol.
-
A.
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.
-
B.
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.
-
C.
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.
-
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 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.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa1e9ec81908d7c26c1c4e43014 |
completed | April 14, 2026, 11:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24bc8464819096b019f1e927d1a9 |
completed | May 8, 2026, 6 p.m. |
| NEDg | Description generation | batch_69fe27e699688190952b6a4b922e3294 |
completed | May 8, 2026, 6:13 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe2896057881908b3947d9649739e7 |
completed | May 8, 2026, 6:16 p.m. |
Created at: April 10, 2026, 1:31 a.m.