Triple
T11359269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanderbilt Health Affiliated Network |
E269040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | healthcare provider network |
C30046
|
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: healthcare provider network Context triple: [Vanderbilt Health Affiliated Network, instanceOf, healthcare provider network]
-
A.
public hospital network
A public hospital network is a coordinated system of government-funded hospitals and healthcare facilities that collaboratively provide accessible, often low-cost or free, medical services to a defined population or region.
-
B.
health insurance provider
A health insurance provider is an organization that offers and manages health coverage plans, collecting premiums and paying for or reimbursing members’ eligible medical expenses according to policy terms.
-
C.
healthcare-related social network
A healthcare-related social network is an online platform that connects patients, caregivers, and healthcare professionals to share experiences, support, and information about health conditions and treatments.
-
D.
healthcare cost management company
A healthcare cost management company analyzes, negotiates, and optimizes medical spending for organizations and individuals to reduce costs while maintaining quality of care.
-
E.
health service purchaser
A health service purchaser is an entity (such as an insurer, government body, or employer) that buys or commissions healthcare services on behalf of a defined population, managing contracts, payments, and performance to ensure value and quality of care.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.