Triple
T29858616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 256 |
E758255
|
entity |
| Predicate | pixelPipelines |
P159575
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [GeForce 256, pixelPipelines, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pixelPipelines Context triple: [GeForce 256, pixelPipelines, 4]
-
A.
pipeline
Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
-
B.
pipelineTo
Indicates that data, output, or results from one process, component, or stage are directed and fed as input into another in a sequential flow.
-
C.
pipelineWidth
chosen
Indicates the width or capacity of a pipeline in a process or data flow.
-
D.
integerPipelines
Indicates a relationship where processes or operations are organized into sequential stages that handle integer data flowing from one step to the next.
-
E.
floatingPointPipelines
Indicates a relationship where one or more entities are involved in, implement, or are associated with pipelines that process floating-point numerical operations.
- 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_69f6768345fc8190bdc72aa7af054375 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:47 p.m.