Triple

T10067538
Position Surface form Disambiguated ID Type / Status
Subject Bradyrhizobium E213137 entity
Predicate genomeFeature P38984 FINISHED
Object large genome size relative to many bacteria 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: large genome size relative to many bacteria | Statement: [Bradyrhizobium, genomeFeature, large genome size relative to many bacteria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: genomeFeature
Context triple: [Bradyrhizobium, genomeFeature, large genome size relative to many bacteria]
  • A. genomeCharacteristic chosen
    Indicates that an entity has a specific property, feature, or attribute related to its genome.
  • B. geneType
    Indicates the specific category or classification of a gene based on its functional or structural characteristics.
  • C. chromosomalLocationOfGene
    Indicates the specific chromosomal position or region where a given gene is located.
  • D. chromosomalLocation
    Indicates the specific position or region on a chromosome where a genetic element (such as a gene or marker) is located.
  • E. alternativeSplicingFeature
    Indicates that a genomic region or element participates in an alternative splicing event, distinguishing it as a feature involved in generating splice variants.
  • 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_69ca83977128819084084eb7d1d8c52a completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cdcff798bc8190a84af7bedea66f0a completed April 2, 2026, 2:09 a.m.
PD Predicate disambiguation batch_69cd4b92573481909389bc6148ae7ea8 completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 8:58 p.m.