Triple
T4979727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office encryption (legacy) |
E111853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | document protection mechanism |
C8241
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: document protection mechanism Context triple: [Microsoft Office encryption (legacy), instanceOf, document protection mechanism]
-
A.
safeguard measure provision
A safeguard measure provision is a legal clause that allows temporary restrictions or corrective actions to protect a party’s interests when unexpected or harmful circumstances arise under an agreement or regulatory framework.
-
B.
view protection regulation
View protection regulation is a set of legal and planning rules designed to preserve or control visual access to significant landscapes, landmarks, or vistas by restricting building heights, placements, or alterations that could obstruct those views.
-
C.
digital rights management technology
chosen
Digital rights management technology encompasses systems and tools designed to control access, usage, and distribution of digital content by enforcing licensing, copyright, and usage policies.
-
D.
security chip
A security chip is a dedicated hardware component designed to securely store cryptographic keys and perform sensitive operations to protect devices and data from unauthorized access and tampering.
-
E.
secure storage facility
A secure storage facility is a highly protected, access-controlled environment designed to safely store valuable, sensitive, or hazardous items against theft, damage, and unauthorized access.
- F. None of above.
Provenance (1 batch)
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_69bd441adc208190b70a033a0741d01e |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:33 p.m.