Triple
T2007406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EAN-13 barcode system |
E43616
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | EAN system |
C1805
|
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: EAN system Context triple: [EAN-13 barcode system, instanceOf, EAN system]
-
A.
European Union quality scheme
A European Union quality scheme is a regulatory framework that identifies and protects the names and characteristics of agricultural products and foodstuffs with specific geographical origins or traditional production methods within the EU.
-
B.
UN/LOCODE identifier
A UN/LOCODE identifier is a standardized five-character code assigned by the United Nations to uniquely identify locations such as ports, cities, and transport hubs used in international trade and logistics.
-
C.
library control number
A library control number is a unique identifier assigned by a library or bibliographic agency to a specific catalog record, enabling precise tracking and retrieval of that item in library systems.
-
D.
ISO standard code set
chosen
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.
-
E.
UN/LOCODE location code
A UN/LOCODE location code is a standardized alphanumeric identifier assigned by the United Nations to uniquely represent specific locations (such as ports, cities, and other transport hubs) used in international trade and transport.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.