Triple

T8612078
Position Surface form Disambiguated ID Type / Status
Subject Nordic nRF51822 E203933 entity
Predicate supportsOTA P83889 FINISHED
Object over-the-air firmware update (DFU) 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: over-the-air firmware update (DFU) | Statement: [Nordic nRF51822, supportsOTA, over-the-air firmware update (DFU)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsOTA
Context triple: [Nordic nRF51822, supportsOTA, over-the-air firmware update (DFU)]
  • A. supportsOneClickUpdates
    Indicates that an entity enables or is compatible with performing updates through a streamlined, single-action (one-click) process.
  • B. requiresFirmware
    Indicates that one entity depends on specific firmware being present or installed on another entity in order to function or be valid.
  • C. previouslySupportedHardware
    Indicates that the subject hardware was supported in the past but is no longer currently supported.
  • D. hasHardwareCompatibilityWith
    Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
  • E. tieneSoporte
    Indicates that one entity provides support, backing, or a supporting structure for another entity.
  • 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.