Triple

T32582088
Position Surface form Disambiguated ID Type / Status
Subject Hash-based Message Authentication Code E832816 entity
Predicate recommendedKeyLengthAtLeast P32227 FINISHED
Object 128 bits 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: 128 bits | Statement: [Hash-based Message Authentication Code, recommendedKeyLengthAtLeast, 128 bits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: recommendedKeyLengthAtLeast
Context triple: [Hash-based Message Authentication Code, recommendedKeyLengthAtLeast, 128 bits]
  • A. recommendedKeyLength chosen
    Indicates the suggested or optimal length that a cryptographic key should have for secure use in a given context.
  • B. supportsKeyLength
    Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
  • C. maximumAuthorizedStrength
    Indicates the highest allowable level or quantity of a resource, capacity, or personnel that is officially permitted.
  • D. consideredInsecureAtKeySize
    Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified key size.
  • E. initialAuthorizedStrength
    Indicates the originally approved or designated level, size, or capacity of a force, group, or resource at the time it was first authorized.
  • 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_69f349289adc81909f4374a58ec35a39 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6f38159d08190980ad639e08f00f4 completed May 3, 2026, 7:04 a.m.
PD Predicate disambiguation batch_69f6e3d7bee48190b94e0beb48a1d7fa completed May 3, 2026, 5:57 a.m.
Created at: May 1, 2026, 1:04 a.m.