Triple
T13636432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1042 |
E325859
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 2464
RFC 2464 is an Internet standard that specifies how IPv6 packets are transmitted over Ethernet networks.
|
E1054069
|
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 2464 | Statement: [RFC 1042, obsoletedBy, RFC 2464]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2464 Context triple: [RFC 1042, obsoletedBy, RFC 2464]
-
A.
RFC 5042
RFC 5042 is an IETF standard that defines the protocol mechanisms and requirements for implementing iWARP, enabling RDMA operations over TCP/IP networks.
-
B.
RFC 2474
RFC 2474 is an IETF standard that defines the Differentiated Services (DiffServ) field in the IPv4 and IPv6 headers to support scalable quality-of-service (QoS) in IP networks.
-
C.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
D.
RFC 1042
RFC 1042 is an early Internet standard that specifies how to encapsulate IP and ARP packets over IEEE 802 local area networks.
-
E.
RFC 2451
RFC 2451 is an Internet Engineering Task Force (IETF) standard that specifies how to use the Twofish encryption algorithm within the IPsec protocol suite for secure network communications.
- 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 2464 Triple: [RFC 1042, obsoletedBy, RFC 2464]
Generated description
RFC 2464 is an Internet standard that specifies how IPv6 packets are transmitted over Ethernet networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2464 Target entity description: RFC 2464 is an Internet standard that specifies how IPv6 packets are transmitted over Ethernet networks.
-
A.
RFC 5042
RFC 5042 is an IETF standard that defines the protocol mechanisms and requirements for implementing iWARP, enabling RDMA operations over TCP/IP networks.
-
B.
RFC 2474
RFC 2474 is an IETF standard that defines the Differentiated Services (DiffServ) field in the IPv4 and IPv6 headers to support scalable quality-of-service (QoS) in IP networks.
-
C.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
D.
RFC 1042
RFC 1042 is an early Internet standard that specifies how to encapsulate IP and ARP packets over IEEE 802 local area networks.
-
E.
RFC 2451
RFC 2451 is an Internet Engineering Task Force (IETF) standard that specifies how to use the Twofish encryption algorithm within the IPsec protocol suite for secure network communications.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af297008190b12256c936714213 |
completed | May 3, 2026, 5:50 p.m. |
| NEDg | Description generation | batch_69f78f1aca288190b4a0af0dd4e96c50 |
completed | May 3, 2026, 6:08 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f790d7bce08190b56fb03b0586ee52 |
completed | May 3, 2026, 6:15 p.m. |
Created at: April 9, 2026, 9:51 p.m.