Triple
T16550164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO/IEC 15693 |
E402050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RFID standard |
C27586
|
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 standard Context triple: [ISO/IEC 15693, instanceOf, RFID standard]
-
A.
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.
-
B.
RFID air interface standard
chosen
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.
-
C.
EPCglobal standard
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.
smart card standard
A smart card standard is a formal specification that defines the physical, electrical, communication, and data structures required to ensure interoperability and security for smart card technologies across different systems and devices.
-
E.
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.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.