Triple
T1404953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES-GCM |
E31669
|
entity |
| Predicate | tagComputation |
P27635
|
FINISHED |
| Object | GHASH over ciphertext and AAD |
—
|
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: GHASH over ciphertext and AAD | Statement: [AES-GCM, tagComputation, GHASH over ciphertext and AAD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tagComputation Context triple: [AES-GCM, tagComputation, GHASH over ciphertext and AAD]
-
A.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
B.
hasLabel
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
C.
markType
Indicates the specific category or kind of mark associated with or applied to an entity.
-
D.
hashtag
Indicates that an entity is associated with or labeled by a specific hashtag, typically used for categorization or topic tagging.
-
E.
trackingType
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.