Triple
T31083659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serial Shipping Container Code |
E792170
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GS1 identification key |
C57401
|
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: GS1 identification key Context triple: [Serial Shipping Container Code, instanceOf, GS1 identification key]
-
A.
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.
-
B.
GS1 data carrier
chosen
A GS1 data carrier is a standardized barcode or RFID tag that encodes GS1 identification keys and related data to enable automatic, accurate identification and tracking of products, assets, or locations across supply chains.
-
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.
globally unique identifier
A globally unique identifier is a value, typically a long numeric or alphanumeric string, that is guaranteed (or practically guaranteed) to be unique across all systems, times, and contexts for reliably identifying an entity.
-
E.
EPCglobal network service
EPCglobal network service is a standardized infrastructure that enables secure sharing, lookup, and retrieval of EPC-related product and event data across organizations in a supply chain.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.