Triple
T33057150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HC-128 |
E845872
|
entity |
| Predicate | securityTarget |
P140382
|
FINISHED |
| Object | 128-bit security |
—
|
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: 128-bit security | Statement: [HC-128, securityTarget, 128-bit security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityTarget Context triple: [HC-128, securityTarget, 128-bit security]
-
A.
securityGoal
Indicates that an action, system, or policy is intended to achieve, support, or satisfy a specified security objective or protection target.
-
B.
securityAlliance
Indicates a formal cooperative relationship in which entities agree to support and protect each other’s security interests, often including mutual defense or coordinated security measures.
-
C.
securityDefinedAs
Indicates that one security concept, mechanism, or configuration is formally specified, characterized, or given meaning in terms of another.
-
D.
securityParameter
chosen
Indicates a relationship where a specific parameter defines or configures the level or characteristics of security applied to an entity or process.
-
E.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 1, 2026, 1:25 a.m.