Triple

T287210
Position Surface form Disambiguated ID Type / Status
Subject RSA E5909 entity
Predicate securityDependsOn P1687 FINISHED
Object difficulty of factoring large composite integers 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: difficulty of factoring large composite integers | Statement: [RSA, securityDependsOn, difficulty of factoring large composite integers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityDependsOn
Context triple: [RSA, securityDependsOn, difficulty of factoring large composite integers]
  • A. securityAspect
    Indicates a relationship where something pertains to, represents, or characterizes a particular aspect or dimension of security.
  • B. securityContext
    Indicates the security-related settings or constraints under which an action, process, or interaction is performed.
  • C. securityType
    Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
  • D. securityMechanism chosen
    Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
  • E. securedVariant
    Indicates that one entity is a security-enhanced or more protected version of another entity.
  • 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_69a25946a7ac8190a78871c210213272 completed Feb. 28, 2026, 2:56 a.m.
NER Named-entity recognition batch_69a25e2ddaa88190b08c40b5823f30a0 completed Feb. 28, 2026, 3:17 a.m.
PD Predicate disambiguation batch_69a25b7c1448819082064f474633acd5 completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 3:02 a.m.