Triple
T22319717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi CERTIFIED WPA |
E551749
|
entity |
| Predicate | securityLevelComparedToWEP |
P29844
|
FINISHED |
| Object | stronger |
—
|
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: stronger | Statement: [Wi‑Fi CERTIFIED WPA, securityLevelComparedToWEP, stronger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityLevelComparedToWEP Context triple: [Wi‑Fi CERTIFIED WPA, securityLevelComparedToWEP, stronger]
-
A.
encryptionLevel
Indicates the degree or strength of cryptographic protection applied to data or communications.
-
B.
isStrongerProtectionThan
chosen
Indicates that one form of protection provides a higher level of security, defense, or safeguarding compared to another.
-
C.
securityLevelDetail
Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
-
D.
typicalSecurityLevel
Indicates the usual or standard security level that is generally applied or expected in a given context or system.
-
E.
consideredInsecureAtKeySize
Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified key size.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15763bf0881908d859f85b4a6ce28 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.