Triple
T28817654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helicobacter |
E727682
|
entity |
| Predicate | genome |
P84745
|
FINISHED |
| Object | circular chromosome |
—
|
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: circular chromosome | Statement: [Helicobacter, genome, circular chromosome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genome Context triple: [Helicobacter, genome, circular chromosome]
-
A.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
-
B.
genomeSize
Indicates the total amount of genetic material (e.g., in base pairs) contained in an organism’s genome.
-
C.
geneticElement
chosen
Indicates that one entity is a genetic element (such as a gene, sequence, or structural unit of genetic material) associated with or characterized by the other entity.
-
D.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
E.
genomeCharacteristic
Indicates that an entity has a specific property, feature, or attribute related to its genome.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f44774819090ba520d0d95c6be |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:33 a.m.