Triple
T30405064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Synergistic Processing Element |
E773455
|
entity |
| Predicate | accessesMainMemoryVia |
P120709
|
FINISHED |
| Object | DMA |
—
|
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: DMA | Statement: [Synergistic Processing Element, accessesMainMemoryVia, DMA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesMainMemoryVia Context triple: [Synergistic Processing Element, accessesMainMemoryVia, DMA]
-
A.
memoryInterface
chosen
Indicates that one entity serves as an interface or access point for interacting with, reading from, or writing to another entity’s memory.
-
B.
memoryController
Indicates a relationship where one entity manages, coordinates, or regulates access to memory resources for another entity or system.
-
C.
builtInMemoryOf
Indicates that something was constructed as a tribute or commemoration to a particular person, group, or event.
-
D.
hasRAM
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
E.
memoryType
Indicates the specific category or kind of memory associated with an entity or process.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 8:03 p.m.