Triple
T29858613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 256 |
E758255
|
entity |
| Predicate | memoryClock |
P66725
|
FINISHED |
| Object | 166 MHz SDR |
—
|
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: 166 MHz SDR | Statement: [GeForce 256, memoryClock, 166 MHz SDR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memoryClock Context triple: [GeForce 256, memoryClock, 166 MHz SDR]
-
A.
memoryController
Indicates a relationship where one entity manages, coordinates, or regulates access to memory resources for another entity or system.
-
B.
memoryCycleTime
Indicates the duration of a complete access cycle for a memory component or system.
-
C.
memory
Indicates that an entity retains, recalls, or is associated with stored information or past experiences.
-
D.
memoryInterface
Indicates that one entity serves as an interface or access point for interacting with, reading from, or writing to another entity’s memory.
-
E.
memoryCharacteristic
chosen
Indicates a relationship where a specific property or quality is attributed to a memory or memory-related entity.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 5:47 p.m.