Triple
T18213166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vincristine |
E436082
|
entity |
| Predicate | hasDoseLimitingToxicity |
P130261
|
FINISHED |
| Object | neurotoxicity |
—
|
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: neurotoxicity | Statement: [vincristine, hasDoseLimitingToxicity, neurotoxicity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoseLimitingToxicity Context triple: [vincristine, hasDoseLimitingToxicity, neurotoxicity]
-
A.
hasNarrowTherapeuticIndex
Indicates that the drug’s effective dose is close to its toxic dose, requiring precise dosing and monitoring to avoid adverse effects.
-
B.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
C.
hasCommonAdverseEffect
Indicates that two or more entities share at least one adverse effect that occurs in response to them.
-
D.
hasHigherDoseStrength
Indicates that one entity has a greater dose strength than another entity in a comparative relationship.
-
E.
isIndicatedAsMonotherapyFor
Indicates that a treatment is recommended or used alone, without combination with other therapies, for a particular condition or purpose.
- F. None of above. chosen
Provenance (4 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e22a26308190a6720b41a9bbfc2d |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:32 a.m.