Triple
T27885324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Core m3-7Y30 |
E705207
|
entity |
| Predicate | maxGraphicsMemory |
P11230
|
FINISHED |
| Object | 32 GB |
—
|
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: 32 GB | Statement: [Intel Core m3-7Y30, maxGraphicsMemory, 32 GB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxGraphicsMemory Context triple: [Intel Core m3-7Y30, maxGraphicsMemory, 32 GB]
-
A.
videoMemorySize
Indicates the amount of video memory associated with a graphics-related component or device.
-
B.
maxRAMOfficial
Indicates the officially specified maximum amount of RAM that is supported or allowed for an entity (such as a device or system).
-
C.
maxUnifiedMemory
chosen
Indicates the maximum amount of unified (shared CPU/GPU) memory that can be allocated or used in a given context.
-
D.
maxRAMUnofficial
Indicates the maximum amount of RAM that can be used or installed in an unofficial or unsupported configuration.
-
E.
mainMemorySize
Indicates the relationship specifying the size or capacity of an entity's main memory.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f639b09d208190a78de29906514a12 |
completed | May 2, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:32 p.m.