Triple
T11798599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTDC ICTS Mark I |
E280566
|
entity |
| Predicate | manufacturer |
P490
|
FINISHED |
| Object | Urban Transportation Development Corporation |
E280560
|
NE 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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Urban Transportation Development Corporation Context triple: [UTDC ICTS Mark I, manufacturer, Urban Transportation Development Corporation]
-
A.
Urban Transportation Development Corporation
chosen
Urban Transportation Development Corporation was a Canadian government-owned company that specialized in designing and manufacturing advanced urban transit systems, including automated light rail vehicles.
-
B.
Triangle Transit Authority
Triangle Transit Authority was the former name of GoTriangle, the regional public transit agency serving North Carolina’s Research Triangle area.
-
C.
Metropolitan Transit Corporation
The Metropolitan Transit Corporation was the former public transit agency that operated bus services in King County, Washington, before being succeeded by King County Metro.
-
D.
Gary Public Transportation Corporation
Gary Public Transportation Corporation is the primary public transit agency for Gary, Indiana, operating local bus services and related transportation within the city and surrounding areas.
-
E.
Transportation Investment Corporation
Transportation Investment Corporation is a British Columbia Crown corporation responsible for overseeing and managing major transportation infrastructure projects and tolling operations in the province.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a03852b80788190b1c83f9b9f755937 |
completed | May 12, 2026, 7:53 p.m. |
Created at: April 8, 2026, 9:42 p.m.