Triple

T20512721
Position Surface form Disambiguated ID Type / Status
Subject Yao’s pseudorandom generator construction E503603 entity
Predicate securityArgument P127292 FINISHED
Object hybrid argument over output 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: hybrid argument over output bits | Statement: [Yao’s pseudorandom generator construction, securityArgument, hybrid argument over output bits]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityArgument
Context triple: [Yao’s pseudorandom generator construction, securityArgument, hybrid argument over output bits]
  • A. securityGuarantee
    Indicates a commitment by one party to protect or defend another party against specified threats or risks.
  • B. securityProof chosen
    Indicates that there exists a formal argument or evidence demonstrating that a system, protocol, or mechanism satisfies specified security properties under defined assumptions.
  • C. securityAssumption
    Indicates that a particular condition, behavior, or property is presumed to hold true for security purposes within a system or protocol.
  • D. securityAspect
    Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
  • E. securityResponse
    Indicates how an entity reacts or takes action in response to a security-related event, threat, or condition.
  • 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_69e0b4b2aa788190ae9eb37c1d73b1f1 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69dcd74c48190b050e25c20154c09 completed April 20, 2026, 9:42 p.m.
PD Predicate disambiguation batch_69e59fdb7ad88190924176c32a195db3 completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:36 a.m.