Triple
T27997722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krka Polska |
E707058
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pharmaceutical company subsidiary |
C28145
|
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: pharmaceutical company subsidiary Context triple: [Krka Polska, instanceOf, pharmaceutical company subsidiary]
-
A.
pharmaceutical division
chosen
A pharmaceutical division is an organizational unit within a company responsible for researching, developing, manufacturing, and marketing medicinal products and therapies.
-
B.
drug discovery company
A drug discovery company is an organization that identifies, designs, and develops new therapeutic compounds to treat diseases, often progressing candidates from early research through preclinical and clinical testing.
-
C.
biopharmaceutical technology company
A biopharmaceutical technology company is an organization that integrates advanced biological research and cutting-edge technological platforms to discover, develop, and manufacture innovative therapeutic products and drug delivery solutions.
-
D.
automotive company subsidiary
An automotive company subsidiary is a legally distinct company controlled by a larger parent automaker that focuses on specific functions such as manufacturing, design, regional operations, or specialized vehicle brands within the overall corporate structure.
-
E.
pharmacy-led health and retail company
A pharmacy-led health and retail company is an organization whose core business centers on pharmacy services and medication management while also offering a broad range of health, wellness, and consumer retail products.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:54 p.m.