Triple
T29858617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 256 |
E758255
|
entity |
| Predicate | textureUnitsPerPipeline |
P168199
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [GeForce 256, textureUnitsPerPipeline, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textureUnitsPerPipeline Context triple: [GeForce 256, textureUnitsPerPipeline, 1]
-
A.
shaderUnits
Indicates the relationship between a graphics processor and the number or configuration of its shader processing units used for rendering and computation.
-
B.
shaderModel
Indicates the specific graphics shading capability level or version that applies to a rendering process, program, or hardware.
-
C.
executionUnits
Indicates a relationship where a process, task, or operation is carried out by one or more specific execution units (such as cores, threads, or processing elements).
-
D.
hasProcessingUnits
Indicates that an entity is equipped with or contains one or more processing units (such as CPUs, GPUs, or similar computational components).
-
E.
usesTexture
Indicates that one entity employs or incorporates the texture of another entity in its appearance, design, or representation.
- F. None of above. chosen
Provenance (4 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_69f6768345fc8190bdc72aa7af054375 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:47 p.m.