Triple
T29372200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YM-2151 |
E744882
|
entity |
| Predicate | hasPanControl |
P194250
|
FINISHED |
| Object | stereo panning per channel |
—
|
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: stereo panning per channel | Statement: [YM-2151, hasPanControl, stereo panning per channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanControl Context triple: [YM-2151, hasPanControl, stereo panning per channel]
-
A.
hasPanoramicView
Indicates that something offers a wide, unobstructed view over a broad surrounding area.
-
B.
hasNavigationControl
Indicates that one entity possesses authority or capability to direct, manage, or influence the movement or course of another entity.
-
C.
hasPanel
Indicates that one entity includes, is equipped with, or is associated with a panel as a component or feature.
-
D.
hasTouchControls
Indicates that an entity supports or is operated through touch-based input controls.
-
E.
hasSlotControls
Indicates that one entity has control over, or is responsible for managing, specific slots or positions associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: April 28, 2026, 2:28 p.m.