Triple
T482566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 791 |
E9801
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object |
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
|
E60448
|
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 950 | Statement: [RFC 791, relatedTo, RFC 950]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 950 Context triple: [RFC 791, relatedTo, RFC 950]
-
A.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
B.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
- 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 950 Triple: [RFC 791, relatedTo, RFC 950]
Generated description
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 950 Target entity description: RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
A.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
B.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f05a7f6c819082b4a5a3e69468a6 |
completed | Feb. 28, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a4711ea1dc8190ac4bf0efaf0890b7 |
completed | March 1, 2026, 5:02 p.m. |
| NEDg | Description generation | batch_69a47275bfd08190ad6a6275b981caf2 |
completed | March 1, 2026, 5:08 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69a472c4e1708190853f390eeb0edf8a |
completed | March 1, 2026, 5:09 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.