Triple
T33186476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electronic Product Code |
E849483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RFID data standard |
C27588
|
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: RFID data standard Context triple: [Electronic Product Code, instanceOf, RFID data standard]
-
A.
RFID air interface standard
An RFID air interface standard defines the communication protocols, signal characteristics, and data exchange rules between RFID tags and readers over the wireless radio frequency link.
-
B.
UHF RFID standard
A UHF RFID standard defines the technical specifications, communication protocols, and performance requirements for ultra-high-frequency radio-frequency identification systems to ensure interoperability and reliable operation across devices and regions.
-
C.
EPCglobal standard
chosen
EPCglobal standard is a set of specifications for using RFID and related technologies to uniquely identify, track, and share information about products and assets across global supply chains.
-
D.
GS1 standard
GS1 standard is a globally recognized system of standards that enables unique identification, accurate data capture, and seamless information sharing across supply chains and industries.
-
E.
RFID reader IC family
A family of RFID reader ICs is a group of integrated circuits designed to generate, transmit, receive, and process radio-frequency signals for reading and sometimes writing data to compatible RFID tags across various standards and applications.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:29 a.m.