Triple
T8612077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordic nRF51822 |
E203933
|
entity |
| Predicate | hasRadioOutputPowerRange |
P83888
|
FINISHED |
| Object | approximately -20 dBm to +4 dBm |
—
|
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: approximately -20 dBm to +4 dBm | Statement: [Nordic nRF51822, hasRadioOutputPowerRange, approximately -20 dBm to +4 dBm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRadioOutputPowerRange Context triple: [Nordic nRF51822, hasRadioOutputPowerRange, approximately -20 dBm to +4 dBm]
-
A.
transmissionPowerType
Indicates the type or category of power used to transmit a signal or data between entities.
-
B.
powerOutputW
Indicates the amount of power produced or delivered by an entity, measured in watts.
-
C.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
D.
hasOutputImpedance
Indicates that an entity (such as a device or component) exhibits a specific impedance at its output terminals.
-
E.
hasPowerSupplyRejectionRatioTypical
Indicates the typical ability of a device or circuit to reject or suppress variations or noise in its power supply from affecting its output.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fdf21c81908ffc6363e98ab871 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.