Triple
T13452512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JPNGO |
E320645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation location code |
C3011
|
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: transportation location code Context triple: [JPNGO, instanceOf, transportation location code]
-
A.
geographic location code
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.
Amtrak station code
An Amtrak station code is a unique three-letter identifier assigned to each train station served by Amtrak for use in reservations, ticketing, and operations.
-
D.
transport hub identifier
chosen
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.
-
E.
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.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:41 p.m.