Triple
T38560168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corynebacterium diphtheriae |
E928055
|
entity |
| Predicate | toxinGeneLocation |
P191438
|
FINISHED |
| Object | lysogenic bacteriophage |
—
|
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: lysogenic bacteriophage | Statement: [Corynebacterium diphtheriae, toxinGeneLocation, lysogenic bacteriophage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toxinGeneLocation Context triple: [Corynebacterium diphtheriae, toxinGeneLocation, lysogenic bacteriophage]
-
A.
toxinGene
Indicates that a gene is associated with the production, regulation, or presence of a toxin.
-
B.
toxinLocation
Indicates the place or environment where a toxin is present, stored, or exerts its effect.
-
C.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
-
D.
chromosomalLocationOfGene
Indicates the specific chromosomal position or region where a given gene is located.
-
E.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
- 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_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.