Triple
T4771229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertzian waves |
E105930
|
entity |
| Predicate | typicalFrequencyRange |
P1685
|
FINISHED |
| Object | radio frequency range |
—
|
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: radio frequency range | Statement: [Hertzian waves, typicalFrequencyRange, radio frequency range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFrequencyRange Context triple: [Hertzian waves, typicalFrequencyRange, radio frequency range]
-
A.
typicalFrequencyUnit
Indicates the unit of measurement typically used to express the frequency of an event, action, or occurrence.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
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.
-
D.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
-
E.
frequencyBand
chosen
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655e5dcc8190a932be9b1baaffb2 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.