Triple
T21228161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mRNA vaccine |
E523135
|
entity |
| Predicate | isTranslatedBy |
P143294
|
FINISHED |
| Object | host ribosomes |
—
|
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: host ribosomes | Statement: [mRNA vaccine, isTranslatedBy, host ribosomes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTranslatedBy Context triple: [mRNA vaccine, isTranslatedBy, host ribosomes]
-
A.
seeTranslatedBy
Indicates that one entity is perceived or visually recognized by another entity through a translated or mediated representation (such as subtitles, dubbing, or other translation mechanisms).
-
B.
hasTranslatedFrom
Indicates that a work or text has been translated from a specified original language or source language.
-
C.
hasTranslated
Indicates that one entity has rendered the content of another entity from one language into a different language.
-
D.
possiblyTranslatedFrom
Indicates that one item may be a translation of another, but this relationship is uncertain or not definitively established.
-
E.
recordTranslatedBy
Indicates that a record has been translated by a particular agent or entity responsible for producing its translated version.
- F. None of above. chosen
Provenance (4 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ad5068819088b203eeba4e6380 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:44 p.m.