Triple
T19451186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subband Codec |
E486616
|
entity |
| Predicate | supportsChannelMode |
P61513
|
FINISHED |
| Object | mono |
—
|
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: mono | Statement: [Subband Codec, supportsChannelMode, mono]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsChannelMode Context triple: [Subband Codec, supportsChannelMode, mono]
-
A.
supportsChannelModes
chosen
Indicates that one entity provides or is compatible with specific operational or configuration modes available on a given channel.
-
B.
supportsChannels
Indicates that one entity is capable of handling, providing, or being compatible with one or more specified channels for communication, distribution, or operation.
-
C.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
D.
requiresChannel
Indicates that an entity or action depends on or must be associated with a specific communication or distribution channel in order to occur or be valid.
-
E.
supportsHAMMode
Indicates that an entity is capable of operating in and providing functionality for HAM (amateur radio) mode.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338db7c081908793f23592ebef6b |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.