Triple
T28859484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Discoba |
E728820
|
entity |
| Predicate | mitochondrialGenomeType |
P29824
|
FINISHED |
| Object | diverse mitochondrial genome structures |
—
|
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: diverse mitochondrial genome structures | Statement: [Discoba, mitochondrialGenomeType, diverse mitochondrial genome structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mitochondrialGenomeType Context triple: [Discoba, mitochondrialGenomeType, diverse mitochondrial genome structures]
-
A.
mitochondrionType
Indicates the specific kind or classification of mitochondrion associated with an entity.
-
B.
hasGenomeType
chosen
Indicates that an entity possesses or is characterized by a specific type or classification of genome.
-
C.
mitochondrialCristaeType
Indicates the specific structural form or organization of the mitochondrial cristae associated with an entity.
-
D.
nucleusType
Indicates the specific kind or classification of nucleus associated with an entity.
-
E.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
- 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_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:46 a.m.