Triple
T5300769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UP-32 |
E119971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional transport office code |
C18357
|
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 office code Context triple: [UP-32, instanceOf, regional transport office code]
-
A.
regional transport plan
A regional transport plan is a strategic framework that outlines long-term goals, policies, and coordinated investments for transportation systems across a defined geographic region.
-
B.
railway station code
A railway station code is a short alphanumeric identifier assigned to a specific train station to uniquely reference it in timetables, ticketing, and railway operations.
-
C.
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.
-
D.
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.
-
E.
public transportation agency
A public transportation agency is an organization responsible for planning, operating, and managing shared transit services such as buses, trains, and other modes to provide mobility for the public within a defined region.
- F. None of above. chosen
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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:53 p.m.