Triple
T2504136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mycobacterium tuberculosis |
E52537
|
entity |
| Predicate | generationTime |
P40195
|
FINISHED |
| Object | approximately 18–24 hours |
—
|
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: approximately 18–24 hours | Statement: [Mycobacterium tuberculosis, generationTime, approximately 18–24 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generationTime Context triple: [Mycobacterium tuberculosis, generationTime, approximately 18–24 hours]
-
A.
generationCount
Indicates the number of times a process, entity, or version has been created, iterated, or regenerated within a sequence or lifecycle.
-
B.
endTimeInGenesis
Indicates the time at which an event or state concludes within the temporal framework defined by the Genesis context or system.
-
C.
generationOf
Indicates that one entity is the origin, creator, or producer of another entity.
-
D.
currentGeneration
Indicates that an entity belongs to or is associated with the presently living or active generation within a temporal or lineage sequence.
-
E.
generation
Indicates the relationship in which one entity produces, creates, or brings another entity into existence.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1cd2db0819087d21ec49ffd9585 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:46 p.m.