Triple
T32092468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIPS R2000 |
E819631
|
entity |
| Predicate | notableSystemUsage |
—
|
GENERATED |
| Object | DECstation workstations |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSystemUsage Context triple: [MIPS R2000, notableSystemUsage, DECstation workstations]
-
A.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
B.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
C.
notableUse
chosen
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
D.
systemNotableCharacteristic
Indicates that a system possesses a particular distinguishing feature or attribute that is especially noteworthy or significant.
-
E.
resourceUsage
Indicates how much of a particular resource is consumed or utilized by an entity, process, or activity over a given context or period.
- 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:25 a.m.