Triple
T6953615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD 5.1 |
E161187
|
entity |
| Predicate | numberOfLFEChannels |
P14387
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [DD 5.1, numberOfLFEChannels, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfLFEChannels Context triple: [DD 5.1, numberOfLFEChannels, 1]
-
A.
hasLFEChannels
Indicates that an entity includes or is associated with one or more Low-Frequency Effects (LFE) audio channels.
-
B.
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.
-
C.
surroundChannelType
Indicates that an audio channel is designated as part of a surround sound configuration (e.g., rear, side, or height channels) rather than a standard stereo or mono channel.
-
D.
numberOfAdditionalChannels
Indicates the quantity of extra channels added beyond a base or default set in a given context.
-
E.
hasNumberOfAmplifierChannels
Indicates the relationship that specifies how many amplifier channels are present or supported in the associated entity.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:29 p.m.