Triple
T33901345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mylan |
E869054
|
entity |
| Predicate | hasKeyTherapeuticAreas |
P151278
|
FINISHED |
| Object | cardiovascular diseases |
—
|
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: cardiovascular diseases | Statement: [Mylan, hasKeyTherapeuticAreas, cardiovascular diseases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyTherapeuticAreas Context triple: [Mylan, hasKeyTherapeuticAreas, cardiovascular diseases]
-
A.
coreTherapeuticArea
Indicates the primary medical or clinical domain in which a therapy, treatment, or product is principally intended to be used.
-
B.
hasUnderlyingCompanyTherapeuticArea
chosen
Indicates that a company is associated with or focused on a particular therapeutic area in its activities or offerings.
-
C.
hasKeyClinicalTrial
Indicates that an entity is associated with a primary or pivotal clinical trial that is especially important for its evaluation or approval.
-
D.
hasKeyBusinessArea
Indicates that an entity is associated with or operates within a particular primary business area or domain.
-
E.
knownForIssuerTherapies
Indicates that an issuer is recognized or notable for providing or developing specific therapies.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:48 a.m.