Triple
T37449012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Trade Center Health Registry |
E930628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health registry |
C65388
|
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 registry Context triple: [World Trade Center Health Registry, instanceOf, health registry]
-
A.
patient registry support program
A patient registry support program is a structured service that helps design, implement, manage, and optimize patient registries to systematically collect, maintain, and analyze health data for clinical, research, and quality-improvement purposes.
-
B.
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.
-
C.
population health management platform
A population health management platform is a system that aggregates and analyzes clinical, claims, and social data to identify risk, coordinate care, and support interventions that improve health outcomes across defined patient populations.
-
D.
population registry
A population registry is a centralized system that records and maintains up-to-date information about individuals residing within a defined jurisdiction, such as their identity, demographic details, and legal status.
-
E.
electronic health record system
An electronic health record system is a digital platform that securely collects, stores, manages, and shares patients’ health information to support clinical care, coordination, and decision-making.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.