Triple
T9897597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BitLocker (device encryption variant) |
E182213
|
entity |
| Predicate | policyControl |
P1652
|
FINISHED |
| Object | can be managed via Group Policy in managed environments |
—
|
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: can be managed via Group Policy in managed environments | Statement: [BitLocker (device encryption variant), policyControl, can be managed via Group Policy in managed environments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyControl Context triple: [BitLocker (device encryption variant), policyControl, can be managed via Group Policy in managed environments]
-
A.
policyTool
chosen
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
B.
policyElement
Indicates that something is a component or constituent part of a broader policy.
-
C.
policyCategory
Indicates the classification or type of policy under which an item, rule, or action is grouped.
-
D.
policyName
Indicates the specific name or title assigned to a policy associated with an entity.
-
E.
policyDriver
Indicates that one entity serves as the motivating cause, rationale, or driving factor behind the creation, adoption, or implementation of a particular policy.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4ab15f881909f75a8e01051dbc4 |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.