Triple
T26408667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keccak |
E663897
|
entity |
| Predicate | hasRoundStructure |
P171402
|
FINISHED |
| Object | 5×5 array of lanes |
—
|
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: 5×5 array of lanes | Statement: [Keccak, hasRoundStructure, 5×5 array of lanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoundStructure Context triple: [Keccak, hasRoundStructure, 5×5 array of lanes]
-
A.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
B.
roundsStructure
Indicates that one entity defines or specifies the organization, sequence, or format of rounds within a process, event, or system.
-
C.
hasTurnStructure
Indicates that an interaction, game, or process is organized into discrete turns that participants take in a defined order.
-
D.
hasRoudNumber
Indicates that an entity is associated with or assigned a specific round number within a sequence of rounds or stages.
-
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_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 26, 2026, 11:36 p.m.