Triple
T27841712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dicke radiometer |
E703696
|
entity |
| Predicate | typicalSwitchingFrequency |
P83979
|
FINISHED |
| Object | kilohertz 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: kilohertz range | Statement: [Dicke radiometer, typicalSwitchingFrequency, kilohertz range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSwitchingFrequency Context triple: [Dicke radiometer, typicalSwitchingFrequency, kilohertz range]
-
A.
operatingFrequencyApproximate
chosen
Indicates an approximate or estimated operating frequency at which an entity functions or is designed to function.
-
B.
typicalFSBFrequency
Indicates the usual or characteristic frequency at which a front-side bus (FSB) operates in a given context.
-
C.
typicalFrequencyUnit
Indicates the unit of measurement typically used to express the frequency of an event, action, or occurrence.
-
D.
typicalSupplyVoltageRange
Indicates the usual minimum-to-maximum voltage range within which a device or component is designed to be normally powered and operate correctly.
-
E.
typicalSupplyVoltage
Indicates the standard or commonly used voltage level at which a device or component is normally supplied or operated.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
Created at: April 27, 2026, 6:03 p.m.