Triple
T31080748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OCSP |
E792087
|
entity |
| Predicate | usesSignatureAlgorithm |
P185960
|
FINISHED |
| Object | digital signatures |
—
|
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: digital signatures | Statement: [OCSP, usesSignatureAlgorithm, digital signatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSignatureAlgorithm Context triple: [OCSP, usesSignatureAlgorithm, digital signatures]
-
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.
requiresSignatureOf
Indicates that one entity must obtain or depend on the formal signature or signed approval of another entity.
-
D.
hasSignatureBit
Indicates that an entity possesses a specific bit or flag used to represent a signature or signed status in a data structure or encoding.
-
E.
canUseAuthenticationAlgorithm
Indicates that an entity is able or permitted to employ a specified authentication algorithm for verifying identity or access.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 29, 2026, 9:02 p.m.