Triple
T16717415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SFI Chain-of-Custody Standard |
E406259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | chain-of-custody standard |
C15261
|
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: chain-of-custody standard Context triple: [SFI Chain-of-Custody Standard, instanceOf, chain-of-custody standard]
-
A.
chain-of-custody certification
chosen
Chain-of-custody certification is a verification process that tracks materials through each stage of production, processing, and distribution to ensure their origin, integrity, and compliance with specified standards.
-
B.
World Customs Organization instrument
A World Customs Organization instrument is an official legal or technical tool—such as a convention, agreement, standard, or guideline—adopted by the WCO to harmonize and facilitate customs procedures and international trade.
-
C.
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.
-
D.
public-key cryptography standard
A public-key cryptography standard is a formally defined specification that governs how asymmetric key pairs are generated, distributed, and used to securely encrypt, decrypt, sign, and verify digital data.
-
E.
standards-related document
A standards-related document is an authoritative publication that defines, explains, or supports the development, implementation, or interpretation of technical or organizational standards.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.