Triple
T286806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFTP |
E5902
|
entity |
| Predicate | encryption |
P5656
|
FINISHED |
| Object | none in base protocol |
—
|
LITERAL 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: none in base protocol | Statement: [TFTP, encryption, none in base protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryption Context triple: [TFTP, encryption, none in base protocol]
-
A.
security
Indicates that an entity provides protection, safety measures, or safeguards to another entity or against specific threats or risks.
-
B.
usesEncryptionAlgorithm
chosen
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
C.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
D.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
E.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
- F. None of above.
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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a2605b372c8190831570aa6532cc96 |
completed | Feb. 28, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69a25b7a8d148190aacdcc8ccb35c7f3 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.