Triple
T8813449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhizobium |
E209718
|
entity |
| Predicate | geneticElement |
P84745
|
FINISHED |
| Object | symbiotic plasmids (sym plasmids) |
—
|
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: symbiotic plasmids (sym plasmids) | Statement: [Rhizobium, geneticElement, symbiotic plasmids (sym plasmids)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geneticElement Context triple: [Rhizobium, geneticElement, symbiotic plasmids (sym plasmids)]
-
A.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
-
B.
geneType
Indicates the specific category or classification of a gene based on its functional or structural characteristics.
-
C.
geneticExchange
Indicates the transfer or sharing of genetic material between entities, resulting in altered or recombined genetic information.
-
D.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
E.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff02e9c819080a8e45ba9ca044e |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.