Triple
T6970701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordnance Factory Board |
E161590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence production organization |
C5343
|
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: defence production organization Context triple: [Ordnance Factory Board, instanceOf, defence production organization]
-
A.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
B.
defense company
chosen
A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
-
C.
nuclear weapons production facility
A nuclear weapons production facility is a highly secured industrial complex where fissile materials are processed and assembled into components and complete systems for nuclear armaments.
-
D.
armoured fighting vehicle manufacturer
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.
-
E.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:30 p.m.