Triple
T26408431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpent cipher |
E663892
|
entity |
| Predicate | roundOperations |
P12126
|
FINISHED |
| Object | linear transformation |
—
|
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: linear transformation | Statement: [Serpent cipher, roundOperations, linear transformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundOperations Context triple: [Serpent cipher, roundOperations, linear transformation]
-
A.
roundOf
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
B.
operationOf
chosen
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
C.
roundCount
Indicates the number of discrete rounds or iterations that have occurred or are allocated within a process, event, or interaction.
-
D.
round
Indicates that an entity has a circular or approximately circular shape or form.
-
E.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 11:36 p.m.