Triple
T19873495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHO-FIC |
E477579
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World Health Organization classification system |
C1782
|
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: World Health Organization classification system Context triple: [WHO-FIC, instanceOf, World Health Organization classification system]
-
A.
World Health Organization designation
A World Health Organization designation is an official label or classification assigned by the WHO to identify and categorize diseases, health threats, or related entities for global monitoring, communication, and policy-making.
-
B.
medical classification system
chosen
A medical classification system is an organized framework that categorizes diseases, conditions, procedures, and related health information using standardized codes to support diagnosis, treatment, research, and healthcare administration.
-
C.
World Health Organization framework
The World Health Organization framework is a structured, evidence-based model that guides global health policy, planning, and interventions by organizing key determinants, systems, and outcomes to improve population health and equity.
-
D.
health classification system
A health classification system is a structured framework used to categorize and code health-related conditions, statuses, and services for consistent recording, analysis, and decision-making.
-
E.
Jaeger classification
Jaeger classification is a system used in ophthalmology to categorize near visual acuity based on standardized reading card print sizes labeled with J-values (e.g., J1, J2, etc.).
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.