Triple
T4238971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.722 |
E94763
|
entity |
| Predicate | lowerSubbandFrequencyRange |
P1685
|
FINISHED |
| Object | 0–4000 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: 0–4000 Hz | Statement: [G.722, lowerSubbandFrequencyRange, 0–4000 Hz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerSubbandFrequencyRange Context triple: [G.722, lowerSubbandFrequencyRange, 0–4000 Hz]
-
A.
lowerBandWidth
Indicates that one entity has a smaller or more limited bandwidth capacity than another.
-
B.
typicalRangeSubsonic
Indicates that the relationship specifies the usual or expected range of values or conditions that apply in a subsonic (below the speed of sound) regime.
-
C.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
D.
lowerLimit
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
-
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.