Triple
T12515627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EdDSA |
E299184
|
entity |
| Predicate | signatureGeneration |
P91204
|
FINISHED |
| Object | deterministic |
—
|
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: deterministic | Statement: [EdDSA, signatureGeneration, deterministic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureGeneration Context triple: [EdDSA, signatureGeneration, deterministic]
-
A.
signatureProducer
Indicates that an entity is responsible for creating or generating a particular signature (e.g., cryptographic, digital, or formal).
-
B.
signatureComputation
chosen
Indicates the process or method by which a signature (such as a cryptographic or digital signature) is generated from given input data.
-
C.
signatureEvent
Indicates an event in which an entity formally signs or authorizes something, such as a document, agreement, or record.
-
D.
signatureType
Indicates the specific kind or category of a signature associated with an entity or action.
-
E.
signatureElement
Indicates that one entity is a component or part of another entity’s signature, such as a defining element within a formal or identifying representation.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.