Triple
T32582089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hash-based Message Authentication Code |
E832816
|
entity |
| Predicate | formalSecurityModel |
P35862
|
FINISHED |
| Object | PRF-based security model |
—
|
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: PRF-based security model | Statement: [Hash-based Message Authentication Code, formalSecurityModel, PRF-based security model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalSecurityModel Context triple: [Hash-based Message Authentication Code, formalSecurityModel, PRF-based security model]
-
A.
securityModelAbbreviation
Indicates that one entity is the standard or commonly used abbreviated form of the name or identifier of a particular security model.
-
B.
securityModelIdentifier
chosen
Indicates the specific security model or framework under which an entity, interaction, or policy is defined or governed.
-
C.
securityModelSimilarTo
Indicates that one entity’s security model is similar or comparable to that of another entity.
-
D.
cryptographicModel
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
-
E.
securityModelChange
Indicates that a change has occurred in the security model governing access, permissions, or protection mechanisms between entities.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:04 a.m.