Triple
T23312922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ebXML |
E590629
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UN/CEFACT standard |
C47501
|
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: UN/CEFACT standard Context triple: [ebXML, instanceOf, UN/CEFACT standard]
-
A.
ISO/IEC standard
An ISO/IEC standard is a formally agreed-upon specification developed jointly by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) that defines common requirements, guidelines, or characteristics for products, services, or systems to ensure quality, safety, interoperability, and consistency across international markets.
-
B.
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.
-
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.
ASN.1 standard
The ASN.1 standard is a formal notation used to define, encode, transmit, and decode structured data in a platform- and language-independent way, commonly used in telecommunications and cryptographic protocols.
-
E.
ISO standard code set
A standardized collection of internationally recognized codes defined by the International Organization for Standardization (ISO) to uniquely and consistently represent specific types of data, such as countries, currencies, languages, or measurements.
- F. None of above. chosen
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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.