Triple
T37707720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nvidia Tegra K1 |
E939237
|
entity |
| Predicate | gpuArchitecture |
P11219
|
FINISHED |
| Object | Kepler |
—
|
NE NERFINISHED |
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: Kepler | Statement: [Nvidia Tegra K1, gpuArchitecture, Kepler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gpuArchitecture Context triple: [Nvidia Tegra K1, gpuArchitecture, Kepler]
-
A.
graphicsArchitecture
chosen
Indicates the underlying design or structural framework that defines how a system’s graphics or visual rendering components are organized and operate.
-
B.
cpuArchitecture
Indicates the type of processor instruction set or hardware architecture that a computing system or component is designed to run on.
-
C.
microarchitectureGeneration
Indicates the specific microarchitecture design generation or family to which a processor or hardware component belongs.
-
D.
gpuType
Indicates the specific kind or model category of GPU associated with an entity.
-
E.
microarchitectureCodename
Indicates the codename assigned to a specific microarchitecture design used in a hardware component or processor.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.