Triple
T8472454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original Amiga chipset |
E200310
|
entity |
| Predicate | maxAudioSampleRate |
P32172
|
FINISHED |
| Object | approximately 28 kHz |
—
|
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: approximately 28 kHz | Statement: [Original Amiga chipset, maxAudioSampleRate, approximately 28 kHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxAudioSampleRate Context triple: [Original Amiga chipset, maxAudioSampleRate, approximately 28 kHz]
-
A.
audioSampleRateHz
chosen
Indicates the number of audio samples captured or played back per second, measured in hertz (Hz), for the associated audio data.
-
B.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
C.
audioSampleRates
Indicates the relationship between an audio resource and the sample rate(s) at which that audio is encoded or can be processed.
-
D.
longFormSampleRate
Indicates the sampling rate used when capturing or representing a long-form version of some data or signal.
-
E.
frameSizeMaximum
Indicates the maximum allowable size or dimensions that a frame can have in a given context.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.