Triple
T12544175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamanaka factors |
E299917
|
entity |
| Predicate | componentRole_Oct4 |
P105809
|
FINISHED |
| Object | core pluripotency regulator |
—
|
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: core pluripotency regulator | Statement: [Yamanaka factors, componentRole_Oct4, core pluripotency regulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentRole_Oct4 Context triple: [Yamanaka factors, componentRole_Oct4, core pluripotency regulator]
-
A.
roleInAktionT4
Indicates that an entity held a specific role or involvement in the Nazi "Aktion T4" euthanasia program.
-
B.
componentAct
Indicates that an action or behavior is performed by a component as part of a larger system or process.
-
C.
portfolioRole
Indicates the specific function, capacity, or position an entity holds within a portfolio or collection of assets.
-
D.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
E.
orthographicRole
Indicates the functional role that a written form or spelling plays within an orthographic system (e.g., as a letter, diacritic, punctuation mark, or other script element).
- 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_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. |
| PDg | Predicate description generation | batch_69d95f5148948190946a575d812b329d |
completed | April 10, 2026, 8:36 p.m. |
Created at: April 8, 2026, 9:57 p.m.