Triple
T63767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH |
E1267
|
entity |
| Predicate | replaced |
P101
|
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: [SSH, replaced, Telnet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Telnet Context triple: [SSH, replaced, 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.
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.
-
C.
SSH
SSH (Secure Shell) is a cryptographic network protocol used to securely access, manage, and transfer data between remote computers over unsecured networks.
-
D.
Tymshare
Tymshare was an influential American time-sharing and computer services company active in the 1960s–1980s that helped pioneer remote computing and software services for businesses.
-
E.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24ee576fc8190b42e5d50767beefb |
completed | Feb. 28, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a25ab9477881908508e3130068bca3 |
completed | Feb. 28, 2026, 3:02 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.