Triple
T1169446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spinraza |
E24879
|
entity |
| Predicate | hasTherapeuticArea |
P20980
|
FINISHED |
| Object | neurology |
—
|
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: neurology | Statement: [Spinraza, hasTherapeuticArea, neurology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTherapeuticArea Context triple: [Spinraza, hasTherapeuticArea, neurology]
-
A.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
B.
hasTargetDisease
chosen
Indicates that an entity (such as a treatment, study, or intervention) is directed toward, intended to affect, or primarily concerned with a specified disease.
-
C.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
D.
hasKeyClinicalTrial
Indicates that an entity is associated with a primary or pivotal clinical trial that is especially important for its evaluation or approval.
-
E.
containsMedicalDistrict
Indicates that one administrative or geographic area includes a designated medical district within its boundaries.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bce821b481908bc278a3fa7973f4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.