Triple
T33173436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amiga 500 Plus |
E849096
|
entity |
| Predicate | mousePort |
P144295
|
FINISHED |
| Object | 2 DE-9 joystick/mouse ports |
—
|
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: 2 DE-9 joystick/mouse ports | Statement: [Amiga 500 Plus, mousePort, 2 DE-9 joystick/mouse ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mousePort Context triple: [Amiga 500 Plus, mousePort, 2 DE-9 joystick/mouse ports]
-
A.
mouseNickname
Indicates that one entity is used as a nickname or informal name for a mouse-related entity (such as a mouse character, device, or individual associated with mice).
-
B.
joystickPort
chosen
Indicates that a device or system has a specific port or interface designated for connecting a joystick.
-
C.
midiPorts
Indicates a relationship where one entity exposes or uses one or more MIDI input/output ports associated with another entity.
-
D.
mainPortOnGozo
Indicates that the referenced port serves as the primary or most important port located on the island of Gozo.
-
E.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port 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_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.