Triple
T37566228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ku-band |
E933962
|
entity |
| Predicate | typicalDownlinkFrequencies |
P184654
|
FINISHED |
| Object | about 10.7 GHz to 12.75 GHz |
—
|
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: about 10.7 GHz to 12.75 GHz | Statement: [Ku-band, typicalDownlinkFrequencies, about 10.7 GHz to 12.75 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDownlinkFrequencies Context triple: [Ku-band, typicalDownlinkFrequencies, about 10.7 GHz to 12.75 GHz]
-
A.
carrierFrequency
Indicates the frequency at which a carrier signal or carrier wave operates in a communication or modulation process.
-
B.
hasFrequencyChannels
Indicates that an entity is associated with, or operates over, one or more specific frequency channels.
-
C.
multipleAccessSchemeDownlink
Indicates that the downlink transmission uses more than one access scheme simultaneously or in combination.
-
D.
downlinkMethod
Indicates the method or technology used to transmit data from a remote system (e.g., satellite or spacecraft) down to a receiving station.
-
E.
frequencyBandLowerLimit
chosen
Indicates the lower boundary value of a specified frequency band in a frequency range or spectrum.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.