Triple
T32226608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | irinotecan |
E823218
|
entity |
| Predicate | isComponentOfRegimen |
P37862
|
FINISHED |
| Object | FOLFIRI |
—
|
NE NERFINISHED |
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: FOLFIRI | Statement: [irinotecan, isComponentOfRegimen, FOLFIRI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isComponentOfRegimen Context triple: [irinotecan, isComponentOfRegimen, FOLFIRI]
-
A.
belongsToRegimen
chosen
Indicates that something is a component or member of a specified regimen or structured treatment plan.
-
B.
isCompleteRegimen
Indicates that a given treatment or course of actions constitutes a full, finished regimen rather than a partial or ongoing one.
-
C.
hasComponentOfFixedDoseCombination
Indicates that an entity is a constituent component within a fixed-dose combination product, where multiple components are combined in set proportions.
-
D.
hasDosingRegimen
Indicates that an entity is associated with a specific dosing regimen, defining how and when a dose is to be administered.
-
E.
regimenDependsOn
Indicates that the applicability or outcome of a regimen is contingent upon another specified factor, condition, or regimen.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 12:38 a.m.