Triple
T7492446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POTS (Plain Old Telephone Service) |
E177036
|
entity |
| Predicate | audioFrequencyRange |
P68289
|
FINISHED |
| Object | voiceband |
—
|
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: voiceband | Statement: [POTS (Plain Old Telephone Service), audioFrequencyRange, voiceband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioFrequencyRange Context triple: [POTS (Plain Old Telephone Service), audioFrequencyRange, voiceband]
-
A.
soundFrequencyRange
Indicates the range of sound frequencies within which the related entity operates, is effective, or is characterized.
-
B.
audioSampleRateHz
Indicates the number of audio samples captured or played back per second, measured in hertz (Hz), for the associated audio data.
-
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.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
E.
frequencyBandSupported
chosen
Indicates that an entity supports operation or functionality within a specified frequency band.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81b431481908214b69c6c8d83bc |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d266d88190982cf5d2ee2e9564 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:43 p.m.