Triple
T7279484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiger Lake |
E163110
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Intel CPU microarchitecture |
C2781
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Intel CPU microarchitecture Context triple: [Tiger Lake, instanceOf, Intel CPU microarchitecture]
-
A.
microprocessor architecture
chosen
Microprocessor architecture is the conceptual design and organization of a computer’s central processing unit, defining its instruction set, data paths, control logic, memory hierarchy, and interfaces to efficiently execute programs.
-
B.
microprocessor
A microprocessor is a compact, integrated circuit that performs the arithmetic, logic, control, and input/output operations of a computer’s central processing unit (CPU) on a single chip.
-
C.
Intel codename
An Intel codename is an internal, often thematic or location-based name used by Intel to identify and reference a specific processor, platform, or technology project before and sometimes alongside its official product branding.
-
D.
microprocessor family
A microprocessor family is a group of closely related microprocessors that share a common architecture, instruction set, and design philosophy, enabling software and hardware compatibility across multiple processor models and generations.
-
E.
CMOS microprocessor
A CMOS microprocessor is a central processing unit implemented using complementary metal-oxide-semiconductor technology, providing high integration, low power consumption, and reliable digital computation on a single chip.
- F. None of above.
Provenance (1 batch)
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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:59 p.m.