Triple
T11798372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urban Transportation Development Corporation |
E280560
|
entity |
| Predicate | product |
P490
|
FINISHED |
| Object | ICTS Mark I vehicles |
—
|
NE GENERATED |
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: ICTS Mark I vehicles Context triple: [Urban Transportation Development Corporation, product, ICTS Mark I vehicles]
-
A.
UTDC ICTS Mark I vehicles
chosen
UTDC ICTS Mark I vehicles are early-generation, fully automated, lightweight rapid transit cars used on systems like Toronto’s Scarborough RT.
-
B.
VAB Mk3 armored vehicle
The VAB Mk3 armored vehicle is a modern, highly mobile 6x6 infantry fighting and support platform developed by Arquus, offering enhanced protection, firepower, and modularity for contemporary battlefield missions.
-
C.
Titus armored vehicle
The Titus armored vehicle is a modern, modular 6x6 wheeled infantry fighting and troop transport platform designed for high mobility and protection in diverse combat and security operations.
-
D.
MAZ-7917 TEL vehicle
The MAZ-7917 TEL vehicle is a large Soviet/Russian eight-axle transporter-erector-launcher designed to carry, erect, and launch intercontinental ballistic missiles such as the RT-2PM Topol.
-
E.
Type 16 maneuver combat vehicle
The Type 16 maneuver combat vehicle is a modern Japanese wheeled tank destroyer designed for rapid deployment and mobile fire support by the Japan Ground Self-Defense Force.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.