Triple
T37566219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ku-band |
E933962
|
entity |
| Predicate | hasFrequencyUpperBound |
P14327
|
FINISHED |
| Object | about 18 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 18 GHz | Statement: [Ku-band, hasFrequencyUpperBound, about 18 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFrequencyUpperBound Context triple: [Ku-band, hasFrequencyUpperBound, about 18 GHz]
-
A.
includesUpperBound
Indicates that the specified range or interval contains and counts its upper limit value as part of the set.
-
B.
isUpperBoundFor
chosen
Indicates that one value is greater than or equal to every element in a given set or collection, serving as an upper limit for them.
-
C.
isBounded
Indicates that a quantity, function, or set does not exceed certain fixed limits in magnitude or extent.
-
D.
hasLowerFrequencyIn
Indicates that one entity occurs or appears less frequently within a specified context than another entity.
-
E.
isUnboundedOn
Indicates that a quantity, function, or process grows without limit and does not remain confined within any finite bounds over a specified domain or context.
- 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.