Triple
T37566229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ku-band |
E933962
|
entity |
| Predicate | typicalUplinkFrequencies |
P205984
|
FINISHED |
| Object | about 12.75 GHz to 14.5 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 12.75 GHz to 14.5 GHz | Statement: [Ku-band, typicalUplinkFrequencies, about 12.75 GHz to 14.5 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalUplinkFrequencies Context triple: [Ku-band, typicalUplinkFrequencies, about 12.75 GHz to 14.5 GHz]
-
A.
carrierFrequency
Indicates the frequency at which a carrier signal or carrier wave operates in a communication or modulation process.
-
B.
frequencyBandUpperLimit
Indicates the upper boundary value of a specified frequency band in which a signal, measurement, or operation is defined.
-
C.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
D.
typicalFSBFrequency
Indicates the usual or characteristic frequency at which a front-side bus (FSB) operates in a given context.
-
E.
multipleAccessSchemeUplink
Indicates that the uplink communication uses multiple access schemes to allow multiple users or signals to share the same transmission resources.
- F. None of above. chosen
Provenance (4 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.