Triple
T36409696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Video Home System |
E896842
|
entity |
| Predicate | audioTrackType |
P89728
|
FINISHED |
| Object | linear mono audio |
—
|
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: linear mono audio | Statement: [Video Home System, audioTrackType, linear mono audio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioTrackType Context triple: [Video Home System, audioTrackType, linear mono audio]
-
A.
audioChannelType
Indicates the specific role or configuration of an audio channel within a multi-channel audio setup (e.g., left, right, center, surround).
-
B.
audioCodingType
Indicates the specific method or standard used to encode or compress an audio signal.
-
C.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
-
D.
audioNetworkingType
Indicates the type of network connection or protocol used for transmitting audio between entities.
-
E.
audioChannelsType
chosen
Indicates the type or configuration of audio channels used in an audio signal or recording (e.g., mono, stereo, surround).
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.