Triple
T33173428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amiga 500 Plus |
E849096
|
entity |
| Predicate | osEnhancement |
P106975
|
FINISHED |
| Object | improved Workbench user interface compared to AmigaOS 1.x |
—
|
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: improved Workbench user interface compared to AmigaOS 1.x | Statement: [Amiga 500 Plus, osEnhancement, improved Workbench user interface compared to AmigaOS 1.x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: osEnhancement Context triple: [Amiga 500 Plus, osEnhancement, improved Workbench user interface compared to AmigaOS 1.x]
-
A.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
B.
enhancedSense
Indicates that an entity possesses a heightened or improved sensory ability compared to a normal or baseline level.
-
C.
enhancementSource
chosen
Indicates that one entity serves as the origin or provider of an enhancement, improvement, or upgrade applied to another entity.
-
D.
hasAlphaEnhancement
Indicates that an entity possesses an increased or augmented alpha-related property, characteristic, or capability compared to a baseline.
-
E.
upgradeOption
Indicates that one entity serves as a possible improved or higher-level alternative to 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_69f3495be8808190bbf427733df08aad |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:29 a.m.