Triple
T33057181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC-256 |
E845873
|
entity |
| Predicate | supportsIVLength |
P5657
|
FINISHED |
| Object | 256-bit IV |
—
|
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: 256-bit IV | Statement: [HC-256, supportsIVLength, 256-bit IV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIVLength Context triple: [HC-256, supportsIVLength, 256-bit IV]
-
A.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
B.
supportsTagLength
Indicates that an entity is capable of handling or enforcing a specified tag length.
-
C.
usesInitializationVectorLength
chosen
Indicates that an entity employs an initialization vector (IV) of a specified length in a cryptographic or security-related operation.
-
D.
keyAndIVLengthEqual
Indicates that the cryptographic key and initialization vector (IV) have the same length.
-
E.
supportsVariableKeyLength
Indicates that an entity is capable of operating correctly with cryptographic keys of varying lengths rather than a single fixed key size.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:25 a.m.