Triple
T8117006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USM |
E189499
|
entity |
| Predicate | securityGranularity |
P81365
|
FINISHED |
| Object | per-user |
—
|
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: per-user | Statement: [USM, securityGranularity, per-user]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityGranularity Context triple: [USM, securityGranularity, per-user]
-
A.
encryptionGranularity
Indicates the level of detail or scope at which data is encrypted within a system or process.
-
B.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
C.
protectionLevel
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
D.
securityPriority
Indicates the relative level of importance or urgency assigned to security-related actions, issues, or protections in comparison to other concerns.
-
E.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
| PDg | Predicate description generation | batch_69cb46635424819085d086972b264280 |
completed | March 31, 2026, 3:58 a.m. |
Created at: March 30, 2026, 5:33 p.m.