Triple
T21627040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POKEY |
E533730
|
entity |
| Predicate | numberOfAudioChannels |
P14387
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [POKEY, numberOfAudioChannels, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfAudioChannels Context triple: [POKEY, numberOfAudioChannels, 4]
-
A.
audioChannels
chosen
Indicates the number or configuration of distinct audio signal paths (such as mono, stereo, or surround) used in a recording, transmission, or playback.
-
B.
audioChannelsType
Indicates the type or configuration of audio channels used in an audio signal or recording (e.g., mono, stereo, surround).
-
C.
hasNumberOfADPCMAChannels
Indicates the quantity of ADPCM (Adaptive Differential Pulse-Code Modulation) channels associated with or supported by an entity.
-
D.
polyphonicChannels
Indicates that an entity supports or involves multiple independent audio or musical channels that can sound simultaneously (polyphony).
-
E.
hasChannelCount
Indicates that an entity is associated with a specific number of channels.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52141e1c8190a861f4bc7cfcb490 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.