Triple
T17354426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genetic and Rare Diseases Information Center |
E421897
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health information service |
C16311
|
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: health information service Context triple: [Genetic and Rare Diseases Information Center, instanceOf, health information service]
-
A.
healthcare services provider
A healthcare services provider is an organization or individual that delivers medical, therapeutic, or preventive health services to patients to diagnose, treat, and manage health conditions.
-
B.
health code
A health code is a set of laws and regulations that establish minimum standards for public health, sanitation, and safety in environments such as restaurants, housing, and workplaces.
-
C.
public health system
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.
-
D.
health care system
A health care system is an organized network of people, institutions, and resources that delivers medical services and public health interventions to maintain and improve the health of a population.
-
E.
health informatics organization
chosen
A health informatics organization is an entity that develops, manages, and applies information systems and data standards to improve the collection, exchange, analysis, and use of health information for clinical, administrative, and public health purposes.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.