Triple
T1437733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AS |
E30594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional transport identifier |
C1045
|
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: regional transport identifier Context triple: [AS, instanceOf, regional transport identifier]
-
A.
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.
-
B.
IATA-like rail station code
chosen
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.
-
C.
railroad rolling stock identifier
A railroad rolling stock identifier is a unique code or marking assigned to each rail vehicle to distinguish it from others for tracking, operations, and maintenance purposes.
-
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.
rapid transit division
A rapid transit division is an organizational unit within a transportation agency responsible for planning, operating, and maintaining high-frequency, high-capacity urban rail or bus rapid transit services.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.