Triple

T957463
Position Surface form Disambiguated ID Type / Status
Subject RC4 E20655 entity
Predicate typicalKeySizeBits P8686 FINISHED
Object 128 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 | Statement: [RC4, typicalKeySizeBits, 128]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalKeySizeBits
Context triple: [RC4, typicalKeySizeBits, 128]
  • A. consideredInsecureAtKeySize
    Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified key size.
  • B. supportsKeyLength chosen
    Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
  • C. typicalKey
    Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
  • D. blockSize
    Indicates the size or capacity of a discrete block unit within a larger structure or system.
  • E. stateSize
    Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population 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_69a493b21f2881908132dcf45dcd2f36 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b3fac2bc8190a66feb70c68899b2 completed March 1, 2026, 9:47 p.m.
PD Predicate disambiguation batch_69a4b2a18ecc8190883f6206fe3b0fb6 completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:40 p.m.