Triple
T7414764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Substitution–permutation network |
E171101
|
entity |
| Predicate | typicalOperationMode |
P26963
|
FINISHED |
| Object | fixed-size blocks |
—
|
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: fixed-size blocks | Statement: [Substitution–permutation network, typicalOperationMode, fixed-size blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOperationMode Context triple: [Substitution–permutation network, typicalOperationMode, fixed-size blocks]
-
A.
typicalPerformanceMode
Indicates the usual or most common way in which an entity performs an action or operates.
-
B.
operatingPattern
chosen
Indicates the characteristic way in which an entity functions or operates over time, such as its typical mode, schedule, or behavioral pattern.
-
C.
typicalOperator
Indicates that an entity commonly or normally performs operations on, or acts upon, another entity in a standard or expected manner.
-
D.
typicalOperatorType
Indicates the usual or most common type or category of operator associated with a given entity or context.
-
E.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.