Triple
T6125370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-band |
E136582
|
entity |
| Predicate | frequencyRangeLower |
P17139
|
FINISHED |
| Object | 2 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: 2 GHz | Statement: [S-band, frequencyRangeLower, 2 GHz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequencyRangeLower Context triple: [S-band, frequencyRangeLower, 2 GHz]
-
A.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
B.
soundFrequencyRange
Indicates the range of sound frequencies within which the related entity operates, is effective, or is characterized.
-
C.
hasLowerFrequencyIn
Indicates that one entity occurs or appears less frequently within a specified context than another entity.
-
D.
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.
-
E.
lowerLimit
chosen
Indicates that one value serves as the minimum or smallest allowable bound or threshold for another value or range.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c2791948190ba33458edfd1ebe8 |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.