Triple
T14427026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pMT1 |
E357722
|
entity |
| Predicate | carriersGene |
P76194
|
FINISHED |
| Object | murine toxin gene |
—
|
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: murine toxin gene | Statement: [pMT1, carriersGene, murine toxin gene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriersGene Context triple: [pMT1, carriersGene, murine toxin gene]
-
A.
isCarrierOf
chosen
Indicates that one entity serves as the bearer, holder, or transmitter of another entity (such as an object, substance, trait, or information).
-
B.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
-
C.
isMajorCarrierOf
Indicates that one entity serves as the primary or principal transporter or conveyor of another entity (such as goods, signals, or passengers).
-
D.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
E.
encodedByGene
Indicates that a particular gene is responsible for producing or specifying the sequence of a given molecule (such as a protein or RNA).
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de911398f08190be85bc0a8bef6b1b |
completed | April 14, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.