Triple
T2125268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAC |
E46408
|
entity |
| Predicate | channelSupport |
P8080
|
FINISHED |
| Object | up to 48 channels in MPEG-4 AAC |
—
|
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: up to 48 channels in MPEG-4 AAC | Statement: [AAC, channelSupport, up to 48 channels in MPEG-4 AAC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelSupport Context triple: [AAC, channelSupport, up to 48 channels in MPEG-4 AAC]
-
A.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
B.
hasApproachChannel
Indicates that one entity provides or is associated with a designated approach channel used for access, navigation, or entry to another entity.
-
C.
channelOrder
Indicates the sequence or priority assigned to channels relative to one another.
-
D.
hasChannel
chosen
Indicates that one entity possesses, provides, or is associated with a particular communication or distribution channel.
-
E.
sisterChannel
Indicates that one channel is a sibling or counterpart to another channel, typically under the same ownership or network.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb57bc6881909f04a407beff33a6 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.