Triple
T2140380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Scientific |
E46745
|
entity |
| Predicate | targetTherapyArea |
P28568
|
FINISHED |
| Object | cardiology |
—
|
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: cardiology | Statement: [Boston Scientific, targetTherapyArea, cardiology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetTherapyArea Context triple: [Boston Scientific, targetTherapyArea, cardiology]
-
A.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
B.
thematicArea
chosen
Indicates the subject or item is associated with, or falls under, a particular thematic area or topic of focus.
-
C.
hasTherapeuticGoal
Indicates that an action, treatment, or intervention is undertaken with the intention of achieving a specific therapeutic or health-related outcome.
-
D.
targetOfIntervention
Indicates that an entity is the object or focus upon which an intervention, treatment, or action is directed.
-
E.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.