Triple
T7636653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data Encryption Standard |
E172893
|
entity |
| Predicate | keySpaceSize |
P77467
|
FINISHED |
| Object | 2^56 |
—
|
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: 2^56 | Statement: [Data Encryption Standard, keySpaceSize, 2^56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySpaceSize Context triple: [Data Encryption Standard, keySpaceSize, 2^56]
-
A.
keySpace
Indicates the logical namespace or partition within a data store or system in which a particular key or set of keys is defined and managed.
-
B.
indexSize
Indicates the size or magnitude of an index associated with an entity, such as its length, capacity, or storage footprint.
-
C.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
-
D.
keyValue
Indicates that one entity functions as a key that is associated with a corresponding value represented by the other entity.
-
E.
stateSizeBytes
Indicates the size of a given state or stateful data in terms of the number of bytes it occupies.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa95e488190962c23609e0890a5 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:57 p.m.