Triple
T2504207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacillus anthracis |
E52538
|
entity |
| Predicate | pXO1Encodes |
P12470
|
FINISHED |
| Object | anthrax toxin components |
—
|
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: anthrax toxin components | Statement: [Bacillus anthracis, pXO1Encodes, anthrax toxin components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pXO1Encodes Context triple: [Bacillus anthracis, pXO1Encodes, anthrax toxin components]
-
A.
encodes
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
B.
plasmids
chosen
Indicates that one entity is a plasmid that carries or is associated with genetic material related to the other entity.
-
C.
geneticMaterialOrganization
Indicates how genetic material is structured, arranged, or organized within or among biological entities.
-
D.
geneticExchange
Indicates the transfer or sharing of genetic material between entities, resulting in altered or recombined genetic information.
-
E.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
- 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_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. |
Created at: March 6, 2026, 9:46 p.m.