Triple
T10682075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEAD_CHACHA20_POLY1305 |
E251780
|
entity |
| Predicate | MACInput |
P19412
|
FINISHED |
| Object | ciphertext and associated data |
—
|
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: ciphertext and associated data | Statement: [AEAD_CHACHA20_POLY1305, MACInput, ciphertext and associated data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MACInput Context triple: [AEAD_CHACHA20_POLY1305, MACInput, ciphertext and associated data]
-
A.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
C.
input
chosen
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
D.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
-
E.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc30be481909922844b539b622d |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.