Triple
T1404956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES-GCM |
E31669
|
entity |
| Predicate | isPreferredOver |
P19077
|
FINISHED |
| Object | AES-CBC-HMAC in many protocols |
—
|
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-CBC-HMAC in many protocols | Statement: [AES-GCM, isPreferredOver, AES-CBC-HMAC in many protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPreferredOver Context triple: [AES-GCM, isPreferredOver, AES-CBC-HMAC in many protocols]
-
A.
isLessPreferredBy
Indicates that one option, item, or entity is chosen or favored less than another by a particular agent or group.
-
B.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
C.
isComparedTo
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
D.
isRankedAbove
chosen
Indicates that one entity holds a higher position or status in an ordered ranking than another entity.
-
E.
appearsBefore
Indicates that one entity occurs, is positioned, or is presented earlier in an ordered sequence than another entity.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bb3a9c81909db2ad91defd87b6 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.