Triple
T11074524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cyclophosphamide |
E261829
|
entity |
| Predicate | isActivatedIn |
P15519
|
FINISHED |
| Object | liver |
—
|
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: liver | Statement: [cyclophosphamide, isActivatedIn, liver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isActivatedIn Context triple: [cyclophosphamide, isActivatedIn, liver]
-
A.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
B.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
C.
isActivatedPreferentiallyIn
Indicates that one entity becomes active or is triggered more readily or predominantly under certain conditions or in the presence of a particular other entity, compared to alternatives.
-
D.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
-
E.
isActive
chosen
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994e32fc8190a6591d9e82b68f75 |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.