Triple
T33926556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E869766
|
entity |
| Predicate | definesAlgorithmUse |
P145700
|
FINISHED |
| Object | hmac-sha2-256 |
—
|
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-sha2-256 | Statement: [RFC 6668, definesAlgorithmUse, hmac-sha2-256]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAlgorithmUse Context triple: [RFC 6668, definesAlgorithmUse, hmac-sha2-256]
-
A.
algorithmicUse
Indicates the use or application of an algorithmic process by one entity in relation to another entity or resource.
-
B.
definesUseOf
Indicates that one entity specifies or determines how another entity is to be used or applied.
-
C.
associatedWithAlgorithm
chosen
Indicates that one entity has a connection or linkage to a specific algorithm, such as using, implementing, or being defined in terms of that algorithm.
-
D.
theoryUsed
Indicates that one entity applies, relies on, or is based upon a particular theory in its reasoning, explanation, or methodology.
-
E.
definitionUses
Indicates that one definition makes use of, depends on, or references another definition.
- 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 1, 2026, 1:49 a.m.