Triple
T26409248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SubBytes |
E663913
|
entity |
| Predicate | inverseUses |
P160524
|
FINISHED |
| Object | inverse AES S-box |
—
|
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: inverse AES S-box | Statement: [SubBytes, inverseUses, inverse AES S-box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inverseUses Context triple: [SubBytes, inverseUses, inverse AES S-box]
-
A.
isInverseOf
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
B.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
C.
definitionUses
Indicates that one definition makes use of, depends on, or references another definition.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61130742c819090e8a55ea2f25145 |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f6018ceb1c8190a6a5f84071659a96 |
completed | May 2, 2026, 1:52 p.m. |
Created at: April 26, 2026, 11:37 p.m.