Triple
T8530328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 870 |
E201928
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 943
RFC 943 is an Internet standards document that superseded RFC 870 by providing updated specifications for early TCP/IP networking protocols.
|
E741735
|
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 943 | Statement: [RFC 870, obsoletedBy, RFC 943]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 943 Context triple: [RFC 870, obsoletedBy, RFC 943]
-
A.
RFC 903
RFC 903 is the Internet standard document that specifies the Reverse Address Resolution Protocol (RARP), which maps link-layer (hardware) addresses to IP addresses in early TCP/IP networks.
-
B.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- 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 943 Triple: [RFC 870, obsoletedBy, RFC 943]
Generated description
RFC 943 is an Internet standards document that superseded RFC 870 by providing updated specifications for early TCP/IP networking protocols.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 943 Target entity description: RFC 943 is an Internet standards document that superseded RFC 870 by providing updated specifications for early TCP/IP networking protocols.
-
A.
RFC 903
RFC 903 is the Internet standard document that specifies the Reverse Address Resolution Protocol (RARP), which maps link-layer (hardware) addresses to IP addresses in early TCP/IP networks.
-
B.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe67546248190b359c845c0161ad3 |
completed | March 31, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6d68d14c81908bde8ca0113f9503 |
completed | April 2, 2026, 1:21 p.m. |
| NEDg | Description generation | batch_69ce6ec1e74081908fc235ffd13ef301 |
completed | April 2, 2026, 1:27 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce6fe13a00819095f5bec408435426 |
completed | April 2, 2026, 1:32 p.m. |
Created at: March 30, 2026, 6:17 p.m.