Triple
T8210209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 5160 |
E191793
|
entity |
| Predicate | inputPorts |
P34282
|
FINISHED |
| Object | keyboard port |
—
|
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: keyboard port | Statement: [IBM 5160, inputPorts, keyboard port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputPorts Context triple: [IBM 5160, inputPorts, keyboard port]
-
A.
hasPorts
chosen
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
B.
audioPorts
Indicates that one entity provides or is equipped with audio input/output ports that can be used or connected by the other entity.
-
C.
midiPorts
Indicates a relationship where one entity exposes or uses one or more MIDI input/output ports associated with another entity.
-
D.
controllerPortCount
Indicates the number of ports available on a given controller.
-
E.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dd881c8190adcbeb2f33d3295c |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.