Triple
T1881430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3501 |
E39860
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
|
E282852
|
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 1730 | Statement: [RFC 3501, obsoletes, RFC 1730]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1730 Context triple: [RFC 3501, obsoletes, RFC 1730]
-
A.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
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 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.
-
D.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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 1730 Triple: [RFC 3501, obsoletes, RFC 1730]
Generated description
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1730 Target entity description: RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
A.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
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 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.
-
D.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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_69a88633e4fc8190b7eb40463e048ec5 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0fb95b48190af5286662c8b9734 |
completed | March 7, 2026, 5 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af9040c20c8190aaae6f22fc893032 |
completed | March 10, 2026, 3:30 a.m. |
| NEDg | Description generation | batch_69af90c873148190804ea5ca9f8c8179 |
completed | March 10, 2026, 3:32 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69af912593ac8190a2f068724f66bef3 |
completed | March 10, 2026, 3:33 a.m. |
Created at: March 4, 2026, 7:34 p.m.