Triple
T25616995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket A |
E642184
|
entity |
| Predicate | usedWithMemoryType |
P9896
|
FINISHED |
| Object | SDR SDRAM (early chipsets) |
—
|
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: SDR SDRAM (early chipsets) | Statement: [Socket A, usedWithMemoryType, SDR SDRAM (early chipsets)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithMemoryType Context triple: [Socket A, usedWithMemoryType, SDR SDRAM (early chipsets)]
-
A.
memoryType
chosen
Indicates the specific category or kind of memory associated with an entity or process.
-
B.
primaryMemoryType
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.
builtInMemoryOf
Indicates that something was constructed as a tribute or commemoration to a particular person, group, or event.
-
E.
hasMemorySlot
Indicates that an entity possesses a specific memory slot or storage location for holding information or data.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 5 p.m.