Triple
T9931182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS 1.2 PRF |
E192650
|
entity |
| Predicate | A_nDefinition |
P91183
|
FINISHED |
| Object | A(1) = HMAC_hash(secret, seed) |
—
|
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: A(1) = HMAC_hash(secret, seed) | Statement: [TLS 1.2 PRF, A_nDefinition, A(1) = HMAC_hash(secret, seed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: A_nDefinition Context triple: [TLS 1.2 PRF, A_nDefinition, A(1) = HMAC_hash(secret, seed)]
-
A.
eraDefinition
Indicates the specific time period or historical era during which something is defined, classified, or considered valid.
-
B.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
C.
abbreviation
Indicates that one term is a shortened or contracted form that stands for another, longer expression.
-
D.
OEIS
Indicates that there is a relationship to the On-Line Encyclopedia of Integer Sequences, typically referencing or identifying a specific integer sequence entry.
-
E.
NPMeaning
Indicates that the predicate specifies the semantic meaning or interpretation associated with a noun phrase in context.
- 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_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. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:43 p.m.