Triple

T20205934
Position Surface form Disambiguated ID Type / Status
Subject Sonos Move E493348 entity
Predicate supportsNetworkStandard P109386 FINISHED
Object Wi‑Fi 802.11 b/g/n 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: Wi‑Fi 802.11 b/g/n | Statement: [Sonos Move, supportsNetworkStandard, Wi‑Fi 802.11 b/g/n]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsNetworkStandard
Context triple: [Sonos Move, supportsNetworkStandard, Wi‑Fi 802.11 b/g/n]
  • A. supportedNetwork chosen
    Indicates that one entity (such as a device, service, or application) is compatible with, operates on, or is designed to work over a specified network or type of network.
  • B. supportsDisplayStandard
    Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
  • C. usesStandard
    Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
  • D. hasSoftwareStandard
    Indicates that an entity conforms to, implements, or is governed by a specified software-related standard.
  • E. isPopularStandardFor
    Indicates that something is widely accepted and commonly used as the standard choice for a particular purpose or context.
  • 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_69da6269614c8190bb40475d9d477358 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66d922ebc8190ae012da8ceba74dd completed April 20, 2026, 6:16 p.m.
PD Predicate disambiguation batch_69e55b14c9d8819095453d0504d9222f completed April 19, 2026, 10:45 p.m.
Created at: April 11, 2026, 11:38 p.m.