Triple
T30725020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kra 1 |
E782253
|
entity |
| Predicate | tRNAIntronType |
P86891
|
FINISHED |
| Object | archaeal-type tRNA introns |
—
|
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: archaeal-type tRNA introns | Statement: [Kra 1, tRNAIntronType, archaeal-type tRNA introns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tRNAIntronType Context triple: [Kra 1, tRNAIntronType, archaeal-type tRNA introns]
-
A.
tRNAIntrons
chosen
Indicates that a transfer RNA (tRNA) molecule contains intron sequences within its coding region.
-
B.
ribosomeType
Indicates the specific kind or category of ribosome associated with or used by an entity.
-
C.
ribosomalRNAFeatures
Indicates features or characteristics specifically associated with ribosomal RNA, such as its structural, functional, or sequence-related properties.
-
D.
InType
Indicates that an entity belongs to, is categorized under, or is an instance of a specified type or class.
-
E.
terminusType
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c5c7be08190ad0f9f4f098c0f99 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:36 p.m.