Triple
T28859405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discoba |
E728818
|
entity |
| Predicate | mitochondrialGenome |
P166509
|
FINISHED |
| Object | often complex and divergent in some members |
—
|
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: often complex and divergent in some members | Statement: [Discoba, mitochondrialGenome, often complex and divergent in some members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mitochondrialGenome Context triple: [Discoba, mitochondrialGenome, often complex and divergent in some members]
-
A.
mitochondrionType
chosen
Indicates the specific kind or classification of mitochondrion associated with an entity.
-
B.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
-
C.
genomeSize
Indicates the total amount of genetic material (e.g., in base pairs) contained in an organism’s genome.
-
D.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
E.
genomeSequenced
Indicates that the complete DNA sequence of an organism’s genome has been determined and recorded.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 6:46 a.m.