Triple
T26408475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Square cipher |
E663893
|
entity |
| Predicate | hasRoundFunction |
P170950
|
FINISHED |
| Object | byte substitution |
—
|
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 substitution | Statement: [Square cipher, hasRoundFunction, byte substitution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoundFunction Context triple: [Square cipher, hasRoundFunction, byte substitution]
-
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.
hasGeneratingFunction
Indicates that one entity serves as the generating function associated with, or defining, another entity.
-
C.
hasLFunction
Indicates that an entity possesses or is associated with a specific L-function, typically representing a complex analytic function linked to its arithmetic or geometric properties.
-
D.
hasChainFunction
Indicates that an entity possesses or is associated with a specific function or role within a chain or sequence of operations.
-
E.
roundFunctionType
Indicates that a function or operation is of a type that performs a rounding transformation on its input values.
- 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_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 26, 2026, 11:36 p.m.