Triple
T31285253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linn LM-1 |
E797786
|
entity |
| Predicate | sampleRate |
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: [Linn LM-1, sampleRate, approximately 28 kHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleRate Context triple: [Linn LM-1, sampleRate, 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.
audioSampleRates
Indicates the relationship between an audio resource and the sample rate(s) at which that audio is encoded or can be processed.
-
C.
referenceRate
Indicates that one entity serves as the benchmark or base rate used to determine or adjust the rate applied to another entity or transaction.
-
D.
soundRecordingSpeed
Indicates the recording speed at which an audio recording was captured or is intended to be played back.
-
E.
samplingResolution
Indicates the level of detail or granularity at which data is sampled or measurements are taken in a process or system.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.