Triple
T12544265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamanaka factors Oct3/4, Sox2, Klf4, and c-Myc |
E299919
|
entity |
| Predicate | cellTypeReprogrammed |
P94935
|
FINISHED |
| Object | mouse fibroblasts |
—
|
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: mouse fibroblasts | Statement: [Yamanaka factors Oct3/4, Sox2, Klf4, and c-Myc, cellTypeReprogrammed, mouse fibroblasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellTypeReprogrammed Context triple: [Yamanaka factors Oct3/4, Sox2, Klf4, and c-Myc, cellTypeReprogrammed, mouse fibroblasts]
-
A.
cellType
Indicates the classification relationship that specifies what type of cell an entity is or is associated with.
-
B.
expressedInCellType
Indicates that something (such as a gene, protein, or molecule) is expressed or present in a specified cell type.
-
C.
cellStates
Indicates the various conditions or phases that a cell can be in at a given time.
-
D.
affectsCellType
chosen
Indicates that one entity produces an effect or change on a specific type of cell.
-
E.
progenitorType
Indicates the type or category of ancestor or originating entity from which another entity descends or is derived.
- 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_69d6ada707008190aaec1238117c9379 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.