Triple
T11073405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Invetech |
E261803
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | life sciences technology company |
C16826
|
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: life sciences technology company Context triple: [Invetech, instanceOf, life sciences technology company]
-
A.
DNA sequencing company
A DNA sequencing company provides services and technologies that determine the precise order of nucleotides in DNA samples for research, clinical, and commercial applications.
-
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.
healthcare technology company
chosen
A healthcare technology company develops and delivers digital tools, platforms, and data-driven solutions that improve the efficiency, quality, and accessibility of medical care and health management.
-
D.
life sciences cluster
A life sciences cluster is a geographically concentrated network of research institutions, companies, and support organizations focused on biotechnology, pharmaceuticals, medical devices, and related health and biological sciences, fostering innovation, collaboration, and economic growth.
-
E.
bioscience research center
A bioscience research center is a specialized facility where scientists conduct experimental and computational studies on living systems to advance knowledge and develop applications in health, agriculture, and biotechnology.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.