Triple
T8814975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nunchuk |
E209754
|
entity |
| Predicate | interfacePort |
P62623
|
FINISHED |
| Object | Wii Remote expansion 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: Wii Remote expansion port | Statement: [Nunchuk, interfacePort, Wii Remote expansion port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interfacePort Context triple: [Nunchuk, interfacePort, Wii Remote expansion port]
-
A.
connectionPort
chosen
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
B.
interfaceFamily
Indicates that one interface belongs to, or is categorized within, a particular family or group of related interfaces.
-
C.
interfaceLocation
Indicates the spatial or logical position where two systems, components, or entities meet and interact.
-
D.
midiPorts
Indicates a relationship where one entity exposes or uses one or more MIDI input/output ports associated with another entity.
-
E.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff1a4448190b5559f440d264442 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.