Triple
T26409249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SubBytes |
E663913
|
entity |
| Predicate | appliedPerRound |
P177102
|
FINISHED |
| Object | once per AES round except key schedule |
—
|
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: once per AES round except key schedule | Statement: [SubBytes, appliedPerRound, once per AES round except key schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedPerRound Context triple: [SubBytes, appliedPerRound, once per AES round except key schedule]
-
A.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
B.
scheduledRounds
Indicates that specific rounds or sessions have been planned and assigned to occur at designated times.
-
C.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
D.
usesVariableNumberOfRounds
Indicates that the action or process operates with a variable, rather than fixed, number of rounds or iterations.
-
E.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
- 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_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 26, 2026, 11:37 p.m.