Triple
T22028281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instant Hotspot |
E544020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tethering feature |
C9032
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: tethering feature Context triple: [Instant Hotspot, instanceOf, tethering feature]
-
A.
wireless file-sharing feature
A wireless file-sharing feature enables users to quickly and securely transfer digital files between nearby devices over radio-based connections without requiring physical cables or internet access.
-
B.
smartphone hardware feature
A smartphone hardware feature is a physical component or built-in device capability—such as a camera, fingerprint sensor, or NFC chip—that enables specific functions and interactions on a smartphone.
-
C.
mobile network feature set
A mobile network feature set is the collection of capabilities, services, and performance characteristics (such as voice, data, messaging, security, and quality-of-service options) provided by a mobile communication network to its users and connected devices.
-
D.
HDMI feature
An HDMI feature is a specific capability or enhancement supported by an HDMI interface—such as audio return, Ethernet over HDMI, or high dynamic range—that defines how audio, video, and data are transmitted and experienced between connected devices.
-
E.
data connectivity technology
chosen
Data connectivity technology encompasses the tools, protocols, and infrastructure that enable seamless, secure, and reliable exchange of data between systems, applications, and devices across diverse networks and environments.
- F. None of above.
Provenance (1 batch)
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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:24 p.m.