Triple
T28583159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPEG-1 Audio Layer III |
E723429
|
entity |
| Predicate | channelModes |
P61513
|
FINISHED |
| Object | stereo |
—
|
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 | Statement: [MPEG-1 Audio Layer III, channelModes, stereo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channelModes Context triple: [MPEG-1 Audio Layer III, channelModes, stereo]
-
A.
supportsChannelModes
chosen
Indicates that one entity provides or is compatible with specific operational or configuration modes available on a given channel.
-
B.
channels
Indicates that one entity serves as a medium, route, or conduit through which another entity is directed, transmitted, or delivered.
-
C.
channelLining
Indicates the presence or application of a protective or functional lining along the interior surface of a channel or conduit.
-
D.
channelAccess
Indicates that one entity has permission or ability to use, view, or interact with a particular communication channel or medium associated with another entity.
-
E.
channelOrder
Indicates the sequence or priority assigned to channels relative to one another.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650cd6ee08190a5c05f83e4b95896 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:16 a.m.