Triple
T1891876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crenarchaeota |
E41890
|
entity |
| Predicate | ribosomalRNAType |
P12472
|
FINISHED |
| Object | distinct archaeal 16S rRNA sequences |
—
|
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: distinct archaeal 16S rRNA sequences | Statement: [Crenarchaeota, ribosomalRNAType, distinct archaeal 16S rRNA sequences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ribosomalRNAType Context triple: [Crenarchaeota, ribosomalRNAType, distinct archaeal 16S rRNA sequences]
-
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.
transcriptionMachinerySimilarity
Indicates that two entities share similar components, structure, or function in their transcription machinery.
-
D.
rimType
Indicates the specific style or configuration of a rim associated with an object or component.
-
E.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb145f96c8190a71bb9e442892e68 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.