Triple
T9931410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Web Token |
E192655
|
entity |
| Predicate | signatureAlgorithmType |
P45884
|
FINISHED |
| Object | HMAC |
—
|
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: HMAC | Statement: [JSON Web Token, signatureAlgorithmType, HMAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureAlgorithmType Context triple: [JSON Web Token, signatureAlgorithmType, HMAC]
-
A.
signatureType
chosen
Indicates the specific kind or category of a signature associated with an entity or action.
-
B.
signatureMaterial
Indicates that a given material is used as the primary medium or substance for a signature.
-
C.
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.
-
D.
signatureProducer
Indicates that an entity is responsible for creating or generating a particular signature (e.g., cryptographic, digital, or formal).
-
E.
signingStandard
Indicates that an entity conforms to, uses, or is governed by a particular standard or specification for signing (e.g., digital signatures or formal approvals).
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.