Triple
T28023465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encrypting File System |
E707748
|
entity |
| Predicate | defaultAlgorithm |
P21840
|
FINISHED |
| Object | AES-based encryption in modern Windows versions |
—
|
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: AES-based encryption in modern Windows versions | Statement: [Encrypting File System, defaultAlgorithm, AES-based encryption in modern Windows versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultAlgorithm Context triple: [Encrypting File System, defaultAlgorithm, AES-based encryption in modern Windows versions]
-
A.
algorithmType
chosen
Indicates the specific kind or category of algorithm associated with an entity or process.
-
B.
defaultSolver
Indicates that one entity functions as the standard or primary solver used by another entity or within a given context.
-
C.
defaultDriver
Indicates that one entity is designated as the primary or standard driver for another entity (such as a vehicle or account).
-
D.
defaultSizeAlgorithm
Indicates the method or procedure used to determine an entity’s size when no explicit size is specified.
-
E.
defaultValue
Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 8:11 p.m.