Triple
T27613957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSA |
E700388
|
entity |
| Predicate | signatureGenerationUses |
P91204
|
FINISHED |
| Object | private key |
—
|
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: private key | Statement: [DSA, signatureGenerationUses, private key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureGenerationUses Context triple: [DSA, signatureGenerationUses, private key]
-
A.
signatureProducer
Indicates that an entity is responsible for creating or generating a particular signature (e.g., cryptographic, digital, or formal).
-
B.
usesSignature
Indicates that one entity employs or relies on the specific signature (e.g., cryptographic, digital, or formal) associated with another entity for validation, identification, or authorization purposes.
-
C.
signatureComputation
chosen
Indicates the process or method by which a signature (such as a cryptographic or digital signature) is generated from given input data.
-
D.
hasSignatureUse
Indicates that an entity is used as an official or primary signature or identifying mark for another entity.
-
E.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:12 p.m.