Triple
T32092468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIPS R2000 |
E819631
|
entity |
| Predicate | notableSystemUsage |
P5773
|
FINISHED |
| Object | DECstation workstations |
E1786160
|
NE 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: DECstation workstations | Statement: [MIPS R2000, notableSystemUsage, DECstation workstations]
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 (4 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddf54bdc8190babcc48830e5b0e5 |
completed | June 14, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:25 a.m.