Triple
T38559740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium ulcerans |
E928043
|
entity |
| Predicate | relatedPathogen |
P206528
|
FINISHED |
| Object | Mycobacterium marinum |
—
|
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: Mycobacterium marinum | Statement: [Mycobacterium ulcerans, relatedPathogen, Mycobacterium marinum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedPathogen Context triple: [Mycobacterium ulcerans, relatedPathogen, Mycobacterium marinum]
-
A.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
B.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
-
C.
pathogen
Indicates that one entity is a disease-causing agent that infects or harms another entity.
-
D.
addressesPathogen
Indicates that an action, intervention, or measure is directed toward counteracting, managing, or mitigating a specific pathogen.
-
E.
includesPathogensOf
Indicates that one entity contains or encompasses the pathogens that are associated with or originate from 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_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.