Triple
T32689717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chubb |
E835821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fire protection company |
C27281
|
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 protection company Context triple: [Chubb, instanceOf, fire protection company]
-
A.
fire protection engineering department
A fire protection engineering department is an organizational unit responsible for the planning, design, implementation, and oversight of systems, policies, and practices that prevent, detect, and control fires to protect people, property, and the environment.
-
B.
firefighting organization
A firefighting organization is a coordinated group responsible for preventing, controlling, and extinguishing fires, as well as responding to related emergencies to protect life, property, and the environment.
-
C.
fire safety equipment manufacturer
chosen
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.
-
D.
fire-safety unit
A fire-safety unit is an organized team or division responsible for preventing, detecting, and responding to fire hazards to protect people, property, and the environment.
-
E.
fire prevention engineer
A fire prevention engineer is a professional who designs, evaluates, and implements systems, codes, and strategies to minimize fire risks and ensure life safety in buildings and facilities.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:09 a.m.