Triple
T33057419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MICKEY 2.0 |
E845878
|
entity |
| Predicate | securityLevelTarget |
P10168
|
FINISHED |
| Object | 80-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: 80-bit security | Statement: [MICKEY 2.0, securityLevelTarget, 80-bit security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityLevelTarget Context triple: [MICKEY 2.0, securityLevelTarget, 80-bit security]
-
A.
securityLevelDetail
Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
-
B.
securityLevelsInclude
Indicates that one entity’s defined security levels contain or encompass the security levels of another entity.
-
C.
securityLevelComponents
Indicates that a particular security level is composed of, or associated with, a specific set of component elements or factors.
-
D.
securityGoal
chosen
Indicates that an action, system, or policy is intended to achieve, support, or satisfy a specified security objective or protection target.
-
E.
encryptionLevel
Indicates the degree or strength of cryptographic protection applied to data or communications.
- 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_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:25 a.m.