Triple
T23277557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurzweil PC2 |
E588762
|
entity |
| Predicate | hasMIDIConnectionType |
P68596
|
FINISHED |
| Object | MIDI In |
—
|
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: MIDI In | Statement: [Kurzweil PC2, hasMIDIConnectionType, MIDI In]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMIDIConnectionType Context triple: [Kurzweil PC2, hasMIDIConnectionType, MIDI In]
-
A.
hasModeConnection
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
B.
hasUSBConnectorType
Indicates the specific type or standard of USB connector associated with a device or component.
-
C.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
-
D.
midiPorts
chosen
Indicates a relationship where one entity exposes or uses one or more MIDI input/output ports associated with another entity.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19578adf48190bdb129a55f86172c |
completed | April 29, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:49 p.m.