Triple
T1096783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secure Real-time Transport Protocol |
E24287
|
entity |
| Predicate | typicalCipher |
P5656
|
FINISHED |
| Object | AES |
—
|
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: AES | Statement: [Secure Real-time Transport Protocol, typicalCipher, AES]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCipher Context triple: [Secure Real-time Transport Protocol, typicalCipher, AES]
-
A.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
B.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
C.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
D.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
E.
usesEncryptionAlgorithm
chosen
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.