Triple
T23143577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFR |
E577526
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business division of Transnet |
C13555
|
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: business division of Transnet Context triple: [TFR, instanceOf, business division of Transnet]
-
A.
public transit operations division
The public transit operations division is responsible for planning, scheduling, managing, and overseeing the daily operation and performance of a region’s public transportation services.
-
B.
public transport maintenance division
A public transport maintenance division is an organizational unit responsible for inspecting, repairing, and servicing vehicles and infrastructure to ensure the safe, reliable, and efficient operation of a public transportation system.
-
C.
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.
-
D.
railroad operating division
chosen
A railroad operating division is a geographically defined segment of a railway system managed as a unit for train operations, crew assignments, dispatching, and maintenance activities.
-
E.
historical transit operating division
A historical transit operating division is an organizational unit within a past or legacy public transportation system responsible for managing and coordinating transit services, personnel, and resources within a specific geographic area or operational domain.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4 p.m.