Triple
T9403313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES-Poly1305 |
E226526
|
entity |
| Predicate | MACAlgorithmFamily |
P56724
|
FINISHED |
| Object | Poly1305 family |
—
|
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: Poly1305 family | Statement: [AES-Poly1305, MACAlgorithmFamily, Poly1305 family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MACAlgorithmFamily Context triple: [AES-Poly1305, MACAlgorithmFamily, Poly1305 family]
-
A.
algorithmFamily
chosen
Indicates that one algorithm belongs to, or is categorized under, a broader family or class of related algorithms.
-
B.
algorithmType
Indicates the specific kind or category of algorithm associated with an entity or process.
-
C.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
D.
cryptographicModel
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
-
E.
macroFamily
Indicates that two or more language families are hypothesized to share a common higher-level genetic origin, forming a larger proposed macro-family grouping.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51bf7e5c8190850b671778496150 |
completed | April 1, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.