Triple
T29371925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TurboBooster |
E744876
|
entity |
| Predicate | audioOutputType |
P89728
|
FINISHED |
| Object | stereo audio output |
—
|
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 audio output | Statement: [TurboBooster, audioOutputType, stereo audio output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioOutputType Context triple: [TurboBooster, audioOutputType, stereo audio output]
-
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.
audioStandard
Indicates the audio format or specification standard that applies to the associated media or device.
-
C.
audioJackType
Indicates the specific kind or standard of audio jack interface used or supported in the relationship.
-
D.
audioChannelsType
chosen
Indicates the type or configuration of audio channels used in an audio signal or recording (e.g., mono, stereo, surround).
-
E.
audioStack
Indicates that one audio element is layered or queued on top of another within an ordered audio sequence or mix.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 2:27 p.m.