Triple
T28695200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naegleria gruberi |
E729393
|
entity |
| Predicate | mitochondrialGenomeIs |
P29824
|
FINISHED |
| Object | typical aerobic mitochondrion |
—
|
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: typical aerobic mitochondrion | Statement: [Naegleria gruberi, mitochondrialGenomeIs, typical aerobic mitochondrion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mitochondrialGenomeIs Context triple: [Naegleria gruberi, mitochondrialGenomeIs, typical aerobic mitochondrion]
-
A.
isMobileGeneticElement
Indicates that the entity is a genetic element capable of moving within or between genomes.
-
B.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
C.
genomeSource
Indicates the origin or provenance of a genome, specifying where or how the genomic data was obtained.
-
D.
mtHaplogroup
Indicates that one entity is classified as having a specific mitochondrial DNA haplogroup associated with the other entity.
-
E.
hasGenomeType
chosen
Indicates that an entity possesses or is characterized by a specific type or classification of 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656ad826c8190a0ac00b608d40467 |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:39 a.m.