Triple
T8530334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 870 |
E201928
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 1700
RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
|
E745992
|
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 1700 | Statement: [RFC 870, obsoletedBy, RFC 1700]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1700 Context triple: [RFC 870, obsoletedBy, RFC 1700]
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
B.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
-
C.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
D.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
E.
RFC 1067
RFC 1067 is an early Internet standard that defined the first Management Information Base (MIB-I) for use with the Simple Network Management Protocol (SNMP).
- 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 1700 Triple: [RFC 870, obsoletedBy, RFC 1700]
Generated description
RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1700 Target entity description: RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
B.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
-
C.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
-
D.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
E.
RFC 1067
RFC 1067 is an early Internet standard that defined the first Management Information Base (MIB-I) for use with the Simple Network Management Protocol (SNMP).
- 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_69cea854e8c881909c62b29d999edde8 |
completed | April 2, 2026, 5:33 p.m. |
| NEDg | Description generation | batch_69cea996a5c48190a12ffe8e282d2d9c |
completed | April 2, 2026, 5:38 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ceadb2d52c8190aada1d797753663e |
completed | April 2, 2026, 5:56 p.m. |
Created at: March 30, 2026, 6:17 p.m.