Triple
T11466481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium |
E271793
|
entity |
| Predicate | acidFast |
P99725
|
FINISHED |
| Object | acid-fast |
—
|
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: acid-fast | Statement: [Mycobacterium, acidFast, acid-fast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acidFast Context triple: [Mycobacterium, acidFast, acid-fast]
-
A.
gramStain
Indicates the result of a Gram staining procedure, specifying how an organism or sample reacts to the Gram stain (e.g., Gram-positive or Gram-negative).
-
B.
bacteriumIdentifiedIn
Indicates that a specific bacterium has been detected, recognized, or confirmed as present in a particular sample, environment, or host.
-
C.
isBacteriaResistant
Indicates that a bacterium is not inhibited or killed by a particular antibiotic or antimicrobial treatment.
-
D.
antigen
Indicates that one entity functions as an antigen in relation to another, typically provoking or being recognized by an immune response.
-
E.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:35 p.m.