Triple
T22755109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-CSCF |
E562819
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency call routing function |
C13225
|
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 call routing function Context triple: [E-CSCF, instanceOf, emergency call routing function]
-
A.
public emergency service system
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.
telephony feature
A telephony feature is a specific capability or function provided by a telecommunication system to enhance, control, or customize the handling of voice and related communications.
-
C.
emergency directive
An emergency directive is an urgent, authoritative instruction issued in response to an immediate threat or crisis, requiring rapid compliance to protect safety, security, or critical operations.
-
D.
civil emergency service
A civil emergency service is a public organization responsible for preparing for, responding to, and managing non-military crises and disasters to protect people, property, and the environment.
-
E.
telephony service
chosen
A telephony service is a system that enables the transmission, routing, and management of voice and related communication over telephone networks or IP-based infrastructures.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:25 p.m.