Triple

T32517032
Position Surface form Disambiguated ID Type / Status
Subject Curve448 E831085 entity
Predicate cryptographicStrength P43793 FINISHED
Object intended to be secure against large-scale classical adversaries 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: intended to be secure against large-scale classical adversaries | Statement: [Curve448, cryptographicStrength, intended to be secure against large-scale classical adversaries]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: cryptographicStrength
Context triple: [Curve448, cryptographicStrength, intended to be secure against large-scale classical adversaries]
  • A. maximumAuthorizedStrength
    Indicates the highest allowable level or quantity of a resource, capacity, or personnel that is officially permitted.
  • B. cryptographicType
    Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
  • C. hasKeyStrength
    Indicates that an entity possesses a primary or defining strength, capability, or advantage.
  • D. cryptographicRelevance chosen
    Indicates that something has significance, impact, or utility within a cryptographic context, such as for security, encryption, or cryptographic analysis.
  • E. consideredInsecureAtKeySize
    Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified 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_69f3492318348190ba37fb6b5f1d67f4 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6cd126fcc8190aa1f1f146e45ec0c completed May 3, 2026, 4:20 a.m.
PD Predicate disambiguation batch_69f6cc1470808190b70cdfd7a6395670 completed May 3, 2026, 4:16 a.m.
Created at: May 1, 2026, 1 a.m.