Triple
T15924294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosovo Protection Corps |
E386167
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil emergency service |
C36685
|
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: civil emergency service Context triple: [Kosovo Protection Corps, instanceOf, civil emergency service]
-
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.
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.
-
C.
civil affairs unit
A civil affairs unit is a military organization responsible for managing relationships and coordination between armed forces and civilian populations, authorities, and institutions in areas of operation.
-
D.
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.
-
E.
civil affairs capacity
Civil affairs capacity is the ability of an organization or force to plan, coordinate, and execute activities that manage relationships and support between civilian populations, local institutions, and military or governmental operations in complex environments.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:52 a.m.