Triple
T19494420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feistel network |
E487732
|
entity |
| Predicate | roundFunctionInput |
P136125
|
FINISHED |
| Object | one half of the block |
—
|
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: one half of the block | Statement: [Feistel network, roundFunctionInput, one half of the block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundFunctionInput Context triple: [Feistel network, roundFunctionInput, one half of the block]
-
A.
roundFunctionType
Indicates that a function or operation is of a type that performs a rounding transformation on its input values.
-
B.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
C.
round
Indicates that an entity has a circular or approximately circular shape or form.
-
D.
usesVariableNumberOfRounds
Indicates that the action or process operates with a variable, rather than fixed, number of rounds or iterations.
-
E.
cryptFunction
Indicates a function or method that performs cryptographic processing, such as encrypting, decrypting, or otherwise transforming data using a cryptographic algorithm.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6349002788190afe7831d008d440f |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.