Triple
T9824084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitrososphaera |
E238608
|
entity |
| Predicate | containsGene |
P84745
|
FINISHED |
| Object | ammonia monooxygenase subunit A |
—
|
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: ammonia monooxygenase subunit A | Statement: [Nitrososphaera, containsGene, ammonia monooxygenase subunit A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsGene Context triple: [Nitrososphaera, containsGene, ammonia monooxygenase subunit A]
-
A.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
B.
hasAllele
Indicates that a biological entity possesses or carries a specific allele variant of a gene.
-
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.
geneType
Indicates the specific category or classification of a gene based on its functional or structural characteristics.
-
E.
targetsGene
Indicates that one entity is directed toward, acts upon, or is intended to affect a specific gene.
- 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb316f8948190ada3738787a5cb6a |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.