Triple
T27613958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSA |
E700388
|
entity |
| Predicate | signatureVerificationUses |
P45884
|
FINISHED |
| Object | public 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: public key | Statement: [DSA, signatureVerificationUses, public key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureVerificationUses Context triple: [DSA, signatureVerificationUses, public key]
-
A.
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.
-
B.
hasSignatureUse
Indicates that an entity is used as an official or primary signature or identifying mark for another entity.
-
C.
signatureMatch
Indicates that two or more items share the same or sufficiently similar signature, confirming they correspond or are equivalent in the relevant context.
-
D.
signatureType
chosen
Indicates the specific kind or category of a signature associated with an entity or action.
-
E.
signatureVariant
Indicates that one signature is an alternative or modified form of another signature, differing in some aspect such as content, format, or representation while remaining related.
- 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_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:12 p.m.