Triple
T359924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edison cylinder phonograph |
E7825
|
entity |
| Predicate | audioQuality |
P9532
|
FINISHED |
| Object | limited frequency range |
—
|
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: limited frequency range | Statement: [Edison cylinder phonograph, audioQuality, limited frequency range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioQuality Context triple: [Edison cylinder phonograph, audioQuality, limited frequency range]
-
A.
soundReproductionMethod
Indicates the method or technique used to reproduce or play back sound.
-
B.
soundCarrier
Indicates that one entity serves as a medium or object that carries, stores, or transmits sound for another entity.
-
C.
hasPerceptualQuality
Indicates that something possesses a particular sensory or perceptual characteristic, such as a color, sound, texture, taste, or smell.
-
D.
soundRecordingSpeed
Indicates the recording speed at which an audio recording was captured or is intended to be played back.
-
E.
acousticProperty
chosen
Indicates the relationship between an entity and its sound-related characteristics, such as loudness, pitch, timbre, or other acoustic features.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebccb8d88190a31f7c443a0c8566 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.