Triple
T29248617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPE/iX |
E741501
|
entity |
| Predicate | designedForHardwarePlatform |
P55922
|
FINISHED |
| Object | HP 3000 |
—
|
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: HP 3000 | Statement: [MPE/iX, designedForHardwarePlatform, HP 3000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForHardwarePlatform Context triple: [MPE/iX, designedForHardwarePlatform, HP 3000]
-
A.
hardwarePlatformFor
chosen
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
-
B.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
D.
runsOnHardware
Indicates that a system, software, or process operates using or is executed on a specified hardware platform.
-
E.
isKeyPlatformFor
Indicates that one entity serves as a primary or foundational platform that enables, supports, or underpins the activities, services, or operations of another entity.
- 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_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 28, 2026, 12:33 p.m.