Triple
T3081741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1122 |
E64273
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1013
RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
|
E330409
|
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 1013 | Statement: [RFC 1122, obsoletes, RFC 1013]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1013 Context triple: [RFC 1122, obsoletes, RFC 1013]
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1012
RFC 1012 is an early Internet standards document that specified requirements and guidelines for host communication protocols before being superseded by later updates.
-
D.
RFC 1010
RFC 1010 was an early Internet standards document that provided an official list of assigned protocol numbers and related parameters before being superseded by later updates.
-
E.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
- 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 1013 Triple: [RFC 1122, obsoletes, RFC 1013]
Generated description
RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1013 Target entity description: RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
-
A.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
C.
RFC 1012
RFC 1012 is an early Internet standards document that specified requirements and guidelines for host communication protocols before being superseded by later updates.
-
D.
RFC 1010
RFC 1010 was an early Internet standards document that provided an official list of assigned protocol numbers and related parameters before being superseded by later updates.
-
E.
RFC 1653
RFC 1653 is an older Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e70b9081908c801d084a6ae992 |
completed | March 8, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b20f4dc9d481908b64d2d2bca0381a |
completed | March 12, 2026, 12:56 a.m. |
| NEDg | Description generation | batch_69b2102e35b08190ad9ca397f0c937da |
completed | March 12, 2026, 1 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b21458b07081909d75886e0d9f88e9 |
completed | March 12, 2026, 1:18 a.m. |
Created at: March 8, 2026, 3:03 p.m.