Triple
T35810425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Instrument Company |
E1035214
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fire-control equipment manufacturer |
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: fire-control equipment manufacturer Context triple: [Ford Instrument Company, instanceOf, fire-control equipment manufacturer]
-
A.
fire safety equipment manufacturer
A fire safety equipment manufacturer is a company that designs, produces, and supplies devices and systems such as fire extinguishers, alarms, sprinklers, and protective gear to prevent, detect, and control fires in residential, commercial, and industrial settings.
-
B.
firearms accessories manufacturer
A firearms accessories manufacturer is a company that designs, produces, and distributes add-on components such as sights, grips, magazines, and suppressors to enhance the functionality, performance, or customization of firearms.
-
C.
arms manufacturer
An arms manufacturer is a company or entity that designs, produces, and supplies weapons, ammunition, and related military equipment for use by armed forces, security agencies, or private clients.
-
D.
munitions facility
A munitions facility is an industrial site where explosive weapons, ammunition, and related components are manufactured, assembled, stored, and sometimes tested under controlled conditions.
-
E.
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.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.