Triple
T29892378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Wing |
E759187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fire-safety unit |
C56393
|
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-safety unit Context triple: [Fire Wing, instanceOf, fire-safety unit]
-
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.
fire service standard
A fire service standard is a formalized set of criteria, procedures, and performance requirements that guide the organization, operation, safety, and effectiveness of fire and emergency response services.
-
C.
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.
-
D.
firefighting training facility
A firefighting training facility is a specialized environment equipped with realistic fire and emergency simulations where firefighters learn, practice, and refine skills in fire suppression, rescue operations, and safety procedures.
-
E.
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.
- F. None of above. chosen
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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:03 p.m.