Triple
T18636833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMMS |
E455572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Location Code |
C1482
|
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: National Location Code Context triple: [GMMS, instanceOf, National Location Code]
-
A.
geographic location code
chosen
A geographic location code is a standardized alphanumeric identifier used to uniquely represent a specific physical area or place on Earth for mapping, analysis, and data exchange.
-
B.
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.
-
C.
geographic code
A geographic code is a standardized alphanumeric identifier used to represent specific geographic areas or locations for purposes such as mapping, analysis, and data organization.
-
D.
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.
-
E.
ISO 3166-2 entry
An ISO 3166-2 entry represents a standardized code and associated metadata that uniquely identifies a principal subdivision (such as a state, province, or region) within a specific country defined in ISO 3166-1.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.