Triple
T38559646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium leprae |
E928041
|
entity |
| Predicate | antimicrobialSusceptibility |
P54931
|
FINISHED |
| Object | dapsone-sensitive |
—
|
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: dapsone-sensitive | Statement: [Mycobacterium leprae, antimicrobialSusceptibility, dapsone-sensitive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antimicrobialSusceptibility Context triple: [Mycobacterium leprae, antimicrobialSusceptibility, dapsone-sensitive]
-
A.
drugSusceptibility
chosen
Indicates that one entity (typically a microorganism, cell, or condition) is vulnerable or responsive to the effects of a specified drug or therapeutic agent.
-
B.
isBacteriaResistant
Indicates that a bacterium is not inhibited or killed by a particular antibiotic or antimicrobial treatment.
-
C.
peptidoglycanTargetingAntibioticSensitivity
Indicates that an entity (such as a bacterium or strain) is sensitive or susceptible to antibiotics that act by targeting peptidoglycan in the cell wall.
-
D.
infectionResult
Indicates that one entity causes or leads to a particular outcome, condition, or state as a result of an infection affecting another entity.
-
E.
bacteriumIdentifiedIn
Indicates that a specific bacterium has been detected, recognized, or confirmed as present in a particular sample, environment, or host.
- 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_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. |
Created at: May 3, 2026, 4:32 p.m.