Triple
T16318751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albendazole |
E396236
|
entity |
| Predicate | isMetabolizedIn |
P50063
|
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: [Albendazole, isMetabolizedIn, liver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMetabolizedIn Context triple: [Albendazole, isMetabolizedIn, liver]
-
A.
isMetabolizedBy
Indicates that a substance is biochemically broken down or transformed through metabolic processes carried out by a specified organism, cell type, or enzyme system.
-
B.
isMetabolizedPrimarilyIn
chosen
Indicates that the substance undergoes its main metabolic processing within the specified biological system or organ.
-
C.
isMetabolizedExtent
Indicates the degree or proportion to which one substance is metabolized by another biological system or agent.
-
D.
isExcretedVia
Indicates that a substance or waste product leaves an organism’s body through a specified anatomical route or excretory mechanism.
-
E.
metabolismType
Indicates the kind of metabolic process or pathway an entity uses to obtain and transform energy or nutrients.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b3e3e081908a996b3e57ca4e32 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.