Triple
T21562363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9-1-1 Emergency System of Puerto Rico |
E532068
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency telephone number system |
C21507
|
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: emergency telephone number system Context triple: [9-1-1 Emergency System of Puerto Rico, instanceOf, emergency telephone number system]
-
A.
public emergency service system
chosen
A public emergency service system is an integrated network of agencies, communication channels, and response resources that coordinates rapid assistance and protection for the public during crises, disasters, and urgent incidents.
-
B.
technical emergency service
A technical emergency service is an organized unit that responds to and manages incidents involving technical hazards, infrastructure failures, and specialized rescue operations using expert equipment and skills.
-
C.
emergency medical service
Emergency medical service is a coordinated system that provides urgent pre-hospital assessment, treatment, and transportation for individuals experiencing acute illness or injury.
-
D.
telephone exchange
A telephone exchange is a system or facility that connects telephone calls by switching voice or data signals between subscribers on a telecommunications network.
-
E.
emergency services district
An emergency services district is a defined geographic area governed by a special-purpose local authority that organizes, funds, and oversees emergency response services such as fire protection, EMS, and rescue operations for the communities within its boundaries.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:29 p.m.