Triple
T8551855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Denise |
E202461
|
entity |
| Predicate | chipsetComponentOf |
P20530
|
FINISHED |
| Object | Enhanced Chip Set |
—
|
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: Enhanced Chip Set | Statement: [Super Denise, chipsetComponentOf, Enhanced Chip Set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chipsetComponentOf Context triple: [Super Denise, chipsetComponentOf, Enhanced Chip Set]
-
A.
chipset
chosen
Indicates that one entity is the chipset (or is associated with the chipset) used by, contained in, or otherwise functionally related to another entity.
-
B.
chipsetBrand
Indicates the brand or manufacturer associated with a device’s chipset.
-
C.
chipsetFamily
Indicates that one chipset belongs to, or is categorized under, a particular chipset family or series.
-
D.
chipSetName
Indicates the specific chipset designation or model name associated with a hardware component or device.
-
E.
systemBoard
Indicates a relationship where a system is associated with, mounted on, or implemented via a particular main circuit board (motherboard) that hosts its core components.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe886fb788190a73e7c76c4f86409 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.