Triple
T7325444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z-Wave |
E168859
|
entity |
| Predicate | competesWith |
P1375
|
FINISHED |
| Object | Zigbee |
E30839
|
NE 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: Zigbee | Statement: [Z-Wave, competesWith, Zigbee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zigbee Context triple: [Z-Wave, competesWith, Zigbee]
-
A.
Zigbee
chosen
Zigbee is a low-power, wireless mesh networking standard commonly used for home automation and Internet of Things (IoT) devices.
-
B.
Z-Wave
Z-Wave is a wireless communication protocol designed primarily for home automation, enabling low-power, reliable control and monitoring of smart devices such as lights, locks, and sensors.
-
C.
IEEE 802.15
IEEE 802.15 is a family of IEEE standards that define wireless personal area networks (WPANs), including technologies like Bluetooth and other short-range, low-power wireless communications.
-
D.
Z-Wave Alliance
Z-Wave Alliance is an industry consortium that develops, promotes, and certifies Z-Wave wireless smart home and IoT technology standards.
-
E.
WirelessHART
WirelessHART is an industrial wireless communication standard designed for reliable, secure, and interoperable field device networking in process automation environments.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68a54cacc81908e3b773441f19566 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f04993408190b73fb46d83a632d5 |
completed | March 27, 2026, 9:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7fa7bfe248190a5def09d6941e114 |
completed | March 28, 2026, 3:57 p.m. |
Created at: March 27, 2026, 3:03 p.m.