Triple
T29681428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VivoBook |
E750961
|
entity |
| Predicate | hasCPUVendor |
P61346
|
FINISHED |
| Object | Intel |
—
|
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: Intel | Statement: [VivoBook, hasCPUVendor, Intel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCPUVendor Context triple: [VivoBook, hasCPUVendor, Intel]
-
A.
CPUVendor
chosen
Indicates that a given CPU is manufactured or branded by a particular vendor.
-
B.
baseCPUVariantName
Indicates that one CPU model is the fundamental or original variant from which another CPU model is derived or named.
-
C.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
-
D.
GPUVendor
Indicates that an entity is the manufacturer or provider of a particular GPU (graphics processing unit).
-
E.
supportsHardwareVendor
Indicates that one entity provides assistance, resources, or endorsement to a hardware vendor in fulfilling its products or services.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6726281c08190a08d1f7a52c34a32 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:10 p.m.