Triple
T1631653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 855 |
E35268
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | Telnet protocol |
E5624
|
NE FINISHED |
How this triple was built (2 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: Telnet protocol | Statement: [RFC 855, basedOn, Telnet protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Telnet protocol Context triple: [RFC 855, basedOn, Telnet protocol]
-
A.
Telnet
chosen
Telnet is a network protocol and command-line tool that allows users to remotely access and manage devices over a text-based terminal connection.
-
B.
RFC 854
RFC 854 is the foundational Internet standard that specifies the Telnet protocol for remote, text-based communication over TCP/IP networks.
-
C.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
D.
Host-to-Host Protocol
Host-to-Host Protocol was an early ARPANET communication protocol that provided reliable end-to-end data transfer between computers, serving as a precursor to modern transport protocols like TCP.
-
E.
TFTP
TFTP (Trivial File Transfer Protocol) is a simple, lightweight file transfer protocol commonly used for tasks like network booting and device configuration in constrained environments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ad71a61de8819095005c222ec50810 |
completed | March 8, 2026, 12:55 p.m. |
Created at: March 4, 2026, 7:28 p.m.