Triple
T36952798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFPA 921 Guide for Fire and Explosion Investigations |
E914117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fire investigation standard |
C37197
|
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 investigation standard Context triple: [NFPA 921 Guide for Fire and Explosion Investigations, instanceOf, fire investigation standard]
-
A.
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.
-
B.
NFPA standard
chosen
An NFPA standard is a consensus-based code or guideline developed by the National Fire Protection Association that establishes minimum requirements for fire, life safety, and related hazards to protect people and property.
-
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.
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.
-
E.
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.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.