Triple
T38559725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium ulcerans |
E928043
|
entity |
| Predicate | mycolactoneFunction |
P190902
|
FINISHED |
| Object | cytotoxic |
—
|
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: cytotoxic | Statement: [Mycobacterium ulcerans, mycolactoneFunction, cytotoxic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mycolactoneFunction Context triple: [Mycobacterium ulcerans, mycolactoneFunction, cytotoxic]
-
A.
cystFunction
Indicates that a cyst exhibits a particular functional status or activity, such as producing substances, affecting surrounding tissues, or participating in physiological processes.
-
B.
capsuleFunction
Indicates that a capsule is designed or used to perform a particular function, role, or therapeutic purpose.
-
C.
clitellumFunction
Indicates the functional role or purpose of an organism’s clitellum in a biological or reproductive context.
-
D.
maneFunction
Indicates that an entity’s primary or central function, role, or purpose is being specified or described.
-
E.
toolFunction
Indicates that one entity serves as a tool used to perform a particular function or achieve a specific purpose for another entity.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd34596288190b8e34a7a20b4c0db |
completed | May 7, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd2e2f00081908b8c820fc073a63c |
completed | May 7, 2026, 5:58 p.m. |
Created at: May 3, 2026, 4:32 p.m.