Triple
T7415097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AddRoundKey |
E171108
|
entity |
| Predicate | inverseOperation |
P21517
|
FINISHED |
| Object | AddRoundKey |
—
|
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: AddRoundKey | Statement: [AddRoundKey, inverseOperation, AddRoundKey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inverseOperation Context triple: [AddRoundKey, inverseOperation, AddRoundKey]
-
A.
opposedOperation
Indicates that one operation is in conflict with, counters, or works against another operation.
-
B.
inverseImage
Indicates the mapping from a set of outputs back to all inputs that are related to those outputs under a given function or relation.
-
C.
isInverseOf
chosen
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
D.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
-
E.
oppositeNumber
Indicates that one number is the additive inverse of the other, such that their sum equals zero.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c643248190a387abba2f482b25 |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.