Triple
T1631612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 854 |
E35267
|
entity |
| Predicate | relatedRFC |
P9936
|
FINISHED |
| Object |
RFC 870
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
|
E201928
|
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 870 | Statement: [RFC 854, relatedRFC, RFC 870]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 870 Context triple: [RFC 854, relatedRFC, RFC 870]
-
A.
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.
-
B.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
C.
RFC 867
RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
D.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
E.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
- 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 870 Triple: [RFC 854, relatedRFC, RFC 870]
Generated description
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 870 Target entity description: RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
A.
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.
-
B.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
C.
RFC 867
RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
D.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
E.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909f5ae98819091ce5e00eb4256a2 |
completed | March 5, 2026, 4:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adb5b50efc8190a89388dcd7cb13aa |
completed | March 8, 2026, 5:45 p.m. |
| NEDg | Description generation | batch_69adb8b2b01c8190997179cdfd55da13 |
completed | March 8, 2026, 5:58 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69adb94aaf348190a28ca8e9d9cacf41 |
completed | March 8, 2026, 6 p.m. |
Created at: March 4, 2026, 7:28 p.m.