Triple
T23277551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurzweil PC2 |
E588762
|
entity |
| Predicate | hasController |
P54128
|
FINISHED |
| Object | pitch bend wheel |
—
|
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: pitch bend wheel | Statement: [Kurzweil PC2, hasController, pitch bend wheel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasController Context triple: [Kurzweil PC2, hasController, pitch bend wheel]
-
A.
hasControlElement
chosen
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
B.
hasControlService
Indicates that one entity provides or performs a control-related service for another entity.
-
C.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
-
D.
hasDetachableControllers
Indicates that an object is equipped with controllers that can be physically removed or separated from its main body.
-
E.
hasNavigationControl
Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course 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_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.