Triple
T10157779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 959 |
E233815
|
entity |
| Predicate | standardizes |
P1371
|
FINISHED |
| Object | File Transfer Protocol |
E42574
|
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: File Transfer Protocol | Statement: [RFC 959, standardizes, File Transfer Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: File Transfer Protocol Context triple: [RFC 959, standardizes, File Transfer Protocol]
-
A.
SFTP (SSH File Transfer Protocol)
SFTP (SSH File Transfer Protocol) is a network protocol that provides encrypted file transfer and management over a secure SSH connection.
-
B.
FTP
FTP, in this context, refers to the Federal Theatre Project, a New Deal program that funded and produced theatrical performances across the United States during the 1930s.
-
C.
FTP
chosen
FTP (File Transfer Protocol) is a standard network protocol used to transfer files between a client and server over a TCP/IP network.
-
D.
FTPS
FTPS is a secure extension of the File Transfer Protocol that adds support for Transport Layer Security (TLS) encryption to protect data in transit.
-
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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3176ac9388190bc76b3cffce93a3d |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:09 p.m.