Triple
T26409240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SubBytes |
E663913
|
entity |
| Predicate | appliesFunction |
P23285
|
FINISHED |
| Object | byte-wise S-box lookup |
—
|
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: byte-wise S-box lookup | Statement: [SubBytes, appliesFunction, byte-wise S-box lookup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesFunction Context triple: [SubBytes, appliesFunction, byte-wise S-box lookup]
-
A.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
B.
associatedFunction
chosen
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
C.
assignedFunction
Indicates that a specific role, duty, or function has been formally allocated to an entity.
-
D.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
E.
appliesOver
Indicates that one entity’s effect, rule, or condition extends across or is valid for a specified range, domain, or set of entities.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 26, 2026, 11:37 p.m.