Triple
T4784907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merck & Co. |
E106451
|
entity |
| Predicate | R&DInvestmentFocus |
P16245
|
FINISHED |
| Object | innovative prescription medicines |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: innovative prescription medicines | Statement: [Merck & Co., R&DInvestmentFocus, innovative prescription medicines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: R&DInvestmentFocus Context triple: [Merck & Co., R&DInvestmentFocus, innovative prescription medicines]
-
A.
innovationArea
chosen
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
B.
researchCenter
Indicates that one entity functions as a research center associated with, operated by, or focused on the other entity.
-
C.
investsIn
Indicates that one entity allocates resources, typically money or capital, into another entity with the expectation of future returns or benefits.
-
D.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
E.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
- F. None of above.
Provenance (3 batches)
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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ae49ec81908f16248d22d1155f |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.