Triple
T5480192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTE-M |
E123448
|
entity |
| Predicate | comparedTo |
P278
|
FINISHED |
| Object | NB-IoT |
E127331
|
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: NB-IoT | Statement: [LTE-M, comparedTo, NB-IoT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NB-IoT Context triple: [LTE-M, comparedTo, NB-IoT]
-
A.
NB-IoT
chosen
NB-IoT (Narrowband Internet of Things) is a low-power wide-area network radio technology standard designed to efficiently connect large numbers of simple, low-throughput IoT devices over licensed cellular spectrum.
-
B.
LTE-M
LTE-M is a low-power wide-area cellular technology based on LTE, designed specifically for connecting Internet of Things (IoT) devices with extended coverage and reduced power consumption.
-
C.
IOT
IOT is the three-letter ISO 3166-1 alpha-3 country code assigned to the British Indian Ocean Territory.
-
D.
LTE
LTE (Long Term Evolution) is a high-speed wireless communication standard for mobile devices and data terminals, widely used as the foundation of 4G cellular networks.
-
E.
Zigbee
Zigbee is a low-power, wireless mesh networking standard commonly used for home automation and Internet of Things (IoT) devices.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf48a2880c8190ad76cf8c3862aede |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:09 p.m.