Triple
T8022314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encrypting File System |
E186766
|
entity |
| Predicate | encryptionGranularity |
P80619
|
FINISHED |
| Object | per-file basis |
—
|
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-file basis | Statement: [Encrypting File System, encryptionGranularity, per-file basis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryptionGranularity Context triple: [Encrypting File System, encryptionGranularity, per-file basis]
-
A.
protectionLevel
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
B.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
C.
timeTravelGranularity
Indicates the level of temporal precision or resolution at which time travel or time-based operations can occur between entities.
-
D.
pricingGranularity
Indicates the level of detail or resolution at which prices are defined, grouped, or applied within a pricing structure or model.
-
E.
encryptionDirection
Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8eab9c81908098e6b17957316c |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:21 p.m.