Triple
T1081842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETSI |
E23962
|
entity |
| Predicate | scope |
P36
|
FINISHED |
| Object | IoT |
E1067
|
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: IoT | Statement: [ETSI, scope, IoT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IoT Context triple: [ETSI, scope, IoT]
-
A.
IOT
IOT is the three-letter ISO 3166-1 alpha-3 country code assigned to the British Indian Ocean Territory.
-
B.
Internet of Things
chosen
The Internet of Things is a network of physical devices embedded with sensors, software, and connectivity that allows them to collect and exchange data autonomously.
-
C.
NB-IoT
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.
-
D.
IEEE 2413 IoT architecture standard
IEEE 2413 IoT architecture standard is a framework that defines a unified, scalable reference architecture and common vocabulary for designing and integrating Internet of Things systems across diverse domains.
-
E.
WSN
WSN is the standard abbreviation used for the Washington Nationals Major League Baseball team.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac538a5d248190bb44c6b27d2c714c |
completed | March 7, 2026, 4:34 p.m. |
Created at: March 1, 2026, 7:42 p.m.