Triple
T12269004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 9293 |
E292423
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 879
RFC 879 is an early Internet standard document that specifies details of the Transmission Control Protocol (TCP), contributing to the foundational design of reliable transport on the Internet.
|
E973135
|
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 879 | Statement: [RFC 9293, obsoletes, RFC 879]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 879 Context triple: [RFC 9293, obsoletes, RFC 879]
-
A.
RFC 877
RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
-
B.
RFC 870
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
C.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
D.
RFC 894
RFC 894 is an Internet standard that specifies how IP datagrams are encapsulated for transmission over Ethernet networks.
-
E.
RFC 857
RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
- 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 879 Triple: [RFC 9293, obsoletes, RFC 879]
Generated description
RFC 879 is an early Internet standard document that specifies details of the Transmission Control Protocol (TCP), contributing to the foundational design of reliable transport on the Internet.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 879 Target entity description: RFC 879 is an early Internet standard document that specifies details of the Transmission Control Protocol (TCP), contributing to the foundational design of reliable transport on the Internet.
-
A.
RFC 877
RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
-
B.
RFC 870
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
C.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
D.
RFC 894
RFC 894 is an Internet standard that specifies how IP datagrams are encapsulated for transmission over Ethernet networks.
-
E.
RFC 857
RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cdea6e881908e13f8259bad6ddc |
completed | April 10, 2026, 3:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e6799088190a5644267733ca2e5 |
completed | May 2, 2026, 3:55 p.m. |
| NEDg | Description generation | batch_69f61f5bc1fc8190af9d74acc307ebe1 |
completed | May 2, 2026, 3:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f62041f2408190ad320fec5283abdd |
completed | May 2, 2026, 4:03 p.m. |
Created at: April 8, 2026, 9:52 p.m.