Triple
T24850854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RNA therapeutics |
E621880
|
entity |
| Predicate | targetsProcess |
P157412
|
FINISHED |
| Object | gene expression |
—
|
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: gene expression | Statement: [RNA therapeutics, targetsProcess, gene expression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsProcess Context triple: [RNA therapeutics, targetsProcess, gene expression]
-
A.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
B.
targetsProvision
Indicates that one entity is the intended recipient or beneficiary of a provision, service, or resource supplied by another entity.
-
C.
targetsSystems
Indicates that an entity is directed at, attacks, or is intended to affect specific systems.
-
D.
targetsProvidedBy
Indicates that one entity supplies or makes available specific targets for another entity to use or act upon.
-
E.
targetWork
Indicates that one entity is the specific work (e.g., document, artwork, or project) that another entity is directed at, refers to, or is primarily concerned with.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f4303fad6c8190844f069164f0904d |
completed | May 1, 2026, 4:46 a.m. |
Created at: April 18, 2026, 5:20 a.m.