Triple
T4238970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.722 |
E94763
|
entity |
| Predicate | upperSubbandFrequencyRange |
P1685
|
FINISHED |
| Object | 4000–8000 Hz |
—
|
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: 4000–8000 Hz | Statement: [G.722, upperSubbandFrequencyRange, 4000–8000 Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperSubbandFrequencyRange Context triple: [G.722, upperSubbandFrequencyRange, 4000–8000 Hz]
-
A.
upperBandWidth
Indicates the maximum bandwidth limit or upper threshold of data transfer capacity allowed or supported in a given context.
-
B.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
C.
upperLimit
Indicates that one entity specifies the maximum allowable value, quantity, or boundary for another entity or condition.
-
D.
transmissionBand
Indicates the specific frequency range or band over which a signal, wave, or transmission is carried or allowed to pass.
-
E.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other entity.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e76b6e0819084d0ce137b5ba74e |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.