Triple
T8507762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DRAM |
E201374
|
entity |
| Predicate | accessGranularity |
P82884
|
FINISHED |
| Object | row-based access |
—
|
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: row-based access | Statement: [DRAM, accessGranularity, row-based access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessGranularity Context triple: [DRAM, accessGranularity, row-based access]
-
A.
securityGranularity
Indicates the level of detail or specificity at which security controls, permissions, or protections are defined and applied within a system or context.
-
B.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
-
C.
encryptionGranularity
Indicates the level of detail or scope at which data is encrypted within a system or process.
-
D.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
E.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
- 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5de18448190a695eec609b34e1a |
completed | March 31, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:14 p.m.