Triple
T14539855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Electronic Injury Surveillance System |
E341139
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | injury surveillance system |
C7556
|
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: injury surveillance system Context triple: [National Electronic Injury Surveillance System, instanceOf, injury surveillance system]
-
A.
disease surveillance program
A disease surveillance program is a systematic, ongoing process of collecting, analyzing, and interpreting health data to detect, monitor, and respond to disease occurrences in a population.
-
B.
healthcare compensation system
A healthcare compensation system is a framework that manages and administers payments, reimbursements, and financial incentives for healthcare providers and organizations based on services delivered, performance metrics, and regulatory requirements.
-
C.
health survey system
A health survey system is a software platform that designs, distributes, collects, and analyzes health-related questionnaires to monitor, assess, and improve individual or population health outcomes.
-
D.
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.
-
E.
public health system
chosen
A public health system is the organized network of people, institutions, resources, and policies that work together to prevent disease, promote health, and protect the well-being of populations.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:22 a.m.