Triple
T4827566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vehicle Factory Jabalpur |
E107862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military vehicle factory |
C12194
|
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: military vehicle factory Context triple: [Vehicle Factory Jabalpur, instanceOf, military vehicle factory]
-
A.
armoured fighting vehicle manufacturer
chosen
An armoured fighting vehicle manufacturer is a company that designs, engineers, and produces military-grade, heavily protected combat vehicles such as tanks, infantry fighting vehicles, and armoured personnel carriers for armed forces and defense clients.
-
B.
automobile factory
An automobile factory is a large-scale industrial facility where raw materials and components are systematically assembled, tested, and finished into complete motor vehicles using coordinated machinery, labor, and production processes.
-
C.
automotive factory
An automotive factory is a large-scale industrial facility where vehicles and their components are systematically designed, manufactured, assembled, and tested using specialized machinery, robotics, and human labor.
-
D.
armored vehicle
An armored vehicle is a heavily protected, often weaponized, transport platform designed to safeguard occupants and critical equipment against ballistic, explosive, and chemical threats in hostile environments.
-
E.
armored military vehicle
An armored military vehicle is a heavily protected, often weaponized, ground transport designed to carry personnel or equipment safely through hostile environments.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.