Triple
T876853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTLIS |
E18936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | trade and transport location identifier |
C1892
|
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: trade and transport location identifier Context triple: [PTLIS, instanceOf, trade and transport location identifier]
-
A.
UN/LOCODE identifier
chosen
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.
-
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.
transport hub identifier
A transport hub identifier uniquely labels a specific transportation node—such as an airport, train station, or bus terminal—to enable unambiguous reference and coordination across systems.
-
D.
IATA-like rail station code
A short, standardized alphanumeric identifier assigned to a railway station, analogous to IATA airport codes, used to uniquely reference stations in timetables, ticketing, and operational systems.
-
E.
ICAO airport code
An ICAO airport code is a four-letter alphanumeric identifier assigned by the International Civil Aviation Organization to uniquely designate airports and aerodromes worldwide for aviation operations and navigation.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.