Triple
T11495011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIC |
E272510
|
entity |
| Predicate | belongsToProtocol |
P3331
|
FINISHED |
| Object | FTP |
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: FTP | Statement: [MIC, belongsToProtocol, FTP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FTP Context triple: [MIC, belongsToProtocol, FTP]
-
A.
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.
-
B.
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.
-
C.
FTPP
FTPP is the acronym for the Fair Trade Practices Program, a regulatory initiative focused on promoting fairness and integrity in commercial trade activities.
-
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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85de183f08190abfa36eaabc61dc6 |
completed | April 10, 2026, 2:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6048a05c88190968f7827c5dd5342 |
completed | April 20, 2026, 10:48 a.m. |
Created at: April 8, 2026, 9:36 p.m.