Triple

T32550579
Position Surface form Disambiguated ID Type / Status
Subject SIGMA protocol family E831961 entity
Predicate typicalAssumptions P7027 FINISHED
Object hardness of discrete logarithm problem — 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: hardness of discrete logarithm problem | Statement: [SIGMA protocol family, typicalAssumptions, hardness of discrete logarithm problem]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalAssumptions
Context triple: [SIGMA protocol family, typicalAssumptions, hardness of discrete logarithm problem]
  • A. typicalAssumption chosen
    Indicates that something is taken as a standard or default assumption that generally holds in typical or normal circumstances.
  • B. typicalIn
    Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
  • C. typicalCircumstance
    Indicates the usual or commonly occurring situation, condition, or context in which an event, action, or relationship typically takes place.
  • D. assumes
    Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
  • E. typicalPerception
    Indicates the usual or most common way an entity is perceived or experienced through the senses.
  • 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_69f34925fd08819084cfe4ec566cb704 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_6a037c894b488190bcbec2eccaff4a01 completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379edf2d88190b492fca86ed23cac completed May 12, 2026, 7:05 p.m.
Created at: May 1, 2026, 1:02 a.m.