Triple
T1295447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARPANET protocol suite |
E27642
|
entity |
| Predicate | notableProtocol |
P28357
|
FINISHED |
| Object | Telnet |
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 | Statement: [ARPANET protocol suite, notableProtocol, Telnet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Telnet Context triple: [ARPANET protocol suite, notableProtocol, Telnet]
-
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.
PuTTY
PuTTY is a widely used free and open-source terminal emulator and network client for Windows and other platforms, supporting protocols like SSH, Telnet, and serial connections.
-
C.
Terminal
Terminal is the built-in command-line interface application for macOS that allows users to interact with the operating system using text-based commands.
-
D.
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.
-
E.
RFC 854
RFC 854 is the foundational Internet standard that specifies the Telnet protocol for remote, text-based communication over TCP/IP networks.
- 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_69a496d6682881909ba658f1c1e0e2b0 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c48bec548190b25d4a74b323cc1b |
completed | March 1, 2026, 10:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acb300d3a0819081a9d19ea1fbdfe2 |
completed | March 7, 2026, 11:21 p.m. |
Created at: March 1, 2026, 7:51 p.m.