Triple
T25617039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Socket 462 |
E642185
|
entity |
| Predicate | notableChipsetSeries |
P5102
|
FINISHED |
| Object | VIA KT133 |
—
|
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: VIA KT133 | Statement: [Socket 462, notableChipsetSeries, VIA KT133]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableChipsetSeries Context triple: [Socket 462, notableChipsetSeries, VIA KT133]
-
A.
usedWithChipsetsFrom
Indicates that something is designed or suitable to be used together with specific chipsets from a given manufacturer or family.
-
B.
notableConsoleFamily
Indicates that a video game console belongs to a family or line of consoles that is considered particularly significant or prominent.
-
C.
chipsetFamily
chosen
Indicates that one chipset belongs to, or is categorized under, a particular chipset family or series.
-
D.
chipsetGeneration
Indicates the generation or version lineage to which a particular chipset belongs.
-
E.
chipSetName
Indicates the specific chipset designation or model name associated with a hardware component or device.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: April 21, 2026, 5 p.m.