Triple
T32510553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Target pharmacy and clinic businesses |
E830918
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | retail health service business unit |
C31723
|
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: retail health service business unit Context triple: [Target pharmacy and clinic businesses, instanceOf, retail health service business unit]
-
A.
retail and services organization
A retail and services organization is a business entity that sells goods and/or provides services directly to consumers or other businesses through various channels such as physical stores, online platforms, or on-site service delivery.
-
B.
healthcare services provider
chosen
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.
-
C.
health service support body
A health service support body is an organization or unit that provides administrative, logistical, technical, or advisory functions to enable and enhance the effective delivery of healthcare services.
-
D.
retail firm
A retail firm is a business organization that purchases goods from manufacturers or wholesalers and sells them directly to consumers through physical or digital channels for profit.
-
E.
retail industry
The retail industry encompasses businesses that sell goods and services directly to consumers through various channels such as physical stores, online platforms, and mobile applications.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1 a.m.