Triple
T25932942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel integrated graphics |
E653478
|
entity |
| Predicate | usesMemoryType |
P9901
|
FINISHED |
| Object | shared system memory |
—
|
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: shared system memory | Statement: [Intel integrated graphics, usesMemoryType, shared system memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMemoryType Context triple: [Intel integrated graphics, usesMemoryType, shared system memory]
-
A.
memoryType
Indicates the specific category or kind of memory associated with an entity or process.
-
B.
primaryMemoryType
chosen
Indicates the main or dominant type of memory associated with or used by an entity in a given context.
-
C.
treatsMemoryAs
Indicates that one entity regards, handles, or interprets another entity specifically as memory (e.g., as a memory resource, location, or storage).
-
D.
hasMemoryIn
Indicates that an entity possesses or stores memory, information, or experiences within a specified context, location, or medium.
-
E.
builtInMemoryOf
Indicates that something was constructed as a tribute or commemoration to a particular person, group, or event.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 22, 2026, 8:37 a.m.