Triple

T32515993
Position Surface form Disambiguated ID Type / Status
Subject secp256k1 E831062 entity
Predicate publicKeyRepresentation P198111 FINISHED
Object points on the curve over F_p 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: points on the curve over F_p | Statement: [secp256k1, publicKeyRepresentation, points on the curve over F_p]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publicKeyRepresentation
Context triple: [secp256k1, publicKeyRepresentation, points on the curve over F_p]
  • A. privateKey
    Indicates that an entity possesses or is associated with a cryptographic private key used for secure authentication, decryption, or signing.
  • B. keyPair
    Indicates a relationship where two cryptographic keys are associated as a matched pair, typically consisting of a public key and a corresponding private key used together for secure operations.
  • C. keyObtainedFrom
    Indicates that a key was acquired or received from a specific source or provider.
  • D. primaryKeySignatures
    Indicates that the referenced key signatures are the main or authoritative signatures associated with the given entity or context.
  • E. privateKeySize
    Indicates the size or length of a private key used in a cryptographic relationship or operation.
  • F. None of above. chosen

Provenance (4 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_69fecb4d02f881909a9ee97ce98000d5 completed May 9, 2026, 5:51 a.m.
PD Predicate disambiguation batch_69fec9846c1c8190b317f0711f0755db completed May 9, 2026, 5:43 a.m.
PDg Predicate description generation batch_69fecb4be24481908bda6197d7fc32f4 completed May 9, 2026, 5:51 a.m.
Created at: May 1, 2026, 1 a.m.