Triple
T29248618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPE/iX |
E741501
|
entity |
| Predicate | designedForComputerType |
P31514
|
FINISHED |
| Object | minicomputer |
—
|
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: minicomputer | Statement: [MPE/iX, designedForComputerType, minicomputer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForComputerType Context triple: [MPE/iX, designedForComputerType, minicomputer]
-
A.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
-
B.
usedInComputerFamily
chosen
Indicates that something (such as a component, technology, or design) is employed within or forms part of a particular family or line of computers.
-
C.
designedForDesktopEnvironment
Indicates that something is intended or optimized to be used within a desktop computing environment.
-
D.
typeOfWorkstation
Indicates the specific category or kind of workstation associated with an entity.
-
E.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system or context.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 12:33 p.m.