Triple
T37449716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacteria |
E930642
|
entity |
| Predicate | containsRibosomalRNAType |
P12472
|
FINISHED |
| Object | 16S rRNA |
—
|
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: 16S rRNA | Statement: [Bacteria, containsRibosomalRNAType, 16S rRNA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRibosomalRNAType Context triple: [Bacteria, containsRibosomalRNAType, 16S rRNA]
-
A.
ribosomeType
Indicates the specific kind or category of ribosome associated with or used by an entity.
-
B.
ribosomalRNAFeatures
chosen
Indicates features or characteristics specifically associated with ribosomal RNA, such as its structural, functional, or sequence-related properties.
-
C.
tRNAIntrons
Indicates that a transfer RNA (tRNA) molecule contains intron sequences within its coding region.
-
D.
hasNitrogenousBase
Indicates that one entity possesses or is associated with a specific nitrogenous base as a component or characteristic.
-
E.
ismRNA
Indicates that one entity is an mRNA molecule corresponding to or derived from another entity (such as a gene or transcript).
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01a18e350481909f848686568d19bc |
completed | May 11, 2026, 9:29 a.m. |
| PD | Predicate disambiguation | batch_6a01a121b67c81908a6c5be9eb8e9ca5 |
completed | May 11, 2026, 9:28 a.m. |
Created at: May 3, 2026, 4:17 p.m.