Triple
T28023466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encrypting File System |
E707748
|
entity |
| Predicate | previousAlgorithm |
P191567
|
FINISHED |
| Object | DESX-based encryption in early 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: DESX-based encryption in early versions | Statement: [Encrypting File System, previousAlgorithm, DESX-based encryption in early versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAlgorithm Context triple: [Encrypting File System, previousAlgorithm, DESX-based encryption in early versions]
-
A.
previousRule
Indicates that one rule directly precedes another rule in an ordered sequence or hierarchy.
-
B.
previousRecord
Indicates that one record directly precedes another in an ordered sequence of records.
-
C.
previousExecutionMethod
Indicates that one entity was formerly used as the method or means by which the other entity was executed.
-
D.
previousRepository
Indicates that one repository directly precedes another in a version, history, or sequence of repositories.
-
E.
previousBehavior
Indicates that an entity’s past actions, conduct, or patterns of behavior are being referenced in relation to a current context or evaluation.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 27, 2026, 8:11 p.m.