Triple
T1777493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1901 |
E39212
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
|
E252133
|
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 1663 | Statement: [RFC 1901, obsoletes, RFC 1663]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1663 Context triple: [RFC 1901, obsoletes, RFC 1663]
-
A.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
B.
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.
-
C.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
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.
- 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 1663 Triple: [RFC 1901, obsoletes, RFC 1663]
Generated description
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1663 Target entity description: RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
A.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
B.
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.
-
C.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
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.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa64b967f08190a73216361b9c2d83 |
completed | March 6, 2026, 5:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae7ed8b7a08190a39f4b90fbf68cd9 |
completed | March 9, 2026, 8:03 a.m. |
| NEDg | Description generation | batch_69ae7f701cc48190a5ca5320ac15117d |
completed | March 9, 2026, 8:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae7ff1fb748190961febf3790f03cf |
completed | March 9, 2026, 8:08 a.m. |
Created at: March 4, 2026, 7:31 p.m.