Triple
T8530330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 870 |
E201928
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 990
RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
|
E743143
|
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 990 | Statement: [RFC 870, obsoletedBy, RFC 990]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 990 Context triple: [RFC 870, obsoletedBy, RFC 990]
-
A.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
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 0960
RFC 0960 is an early Internet standards document that specified aspects of TCP/IP networking behavior later superseded by RFC 1122.
-
D.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
E.
RFC 977
RFC 977 is the original specification that standardized the Network News Transfer Protocol (NNTP) used for reading and distributing Usenet news.
- 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 990 Triple: [RFC 870, obsoletedBy, RFC 990]
Generated description
RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 990 Target entity description: RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
-
A.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
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 0960
RFC 0960 is an early Internet standards document that specified aspects of TCP/IP networking behavior later superseded by RFC 1122.
-
D.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
E.
RFC 977
RFC 977 is the original specification that standardized the Network News Transfer Protocol (NNTP) used for reading and distributing Usenet news.
- 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_69ce890333d08190b510d970e6d6fee5 |
completed | April 2, 2026, 3:19 p.m. |
| NEDg | Description generation | batch_69ce8a9ba0448190ae7637f24b8a8032 |
completed | April 2, 2026, 3:26 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce8bda33548190a8f6985a48d65a39 |
completed | April 2, 2026, 3:31 p.m. |
Created at: March 30, 2026, 6:17 p.m.