Triple
T31101958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Leekie |
E792696
|
entity |
| Predicate | researchFocusInStory |
P24329
|
FINISHED |
| Object | human genetic modification |
—
|
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: human genetic modification | Statement: [Dr. Leekie, researchFocusInStory, human genetic modification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchFocusInStory Context triple: [Dr. Leekie, researchFocusInStory, human genetic modification]
-
A.
researchFocusSince
Indicates the point in time since which an entity has maintained a particular research focus or area of study.
-
B.
researchTopic
chosen
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
C.
narrativeFocusOfWork
Indicates that a particular element (such as a character, event, or theme) is the primary narrative focus or central subject of a given work.
-
D.
creativeWorkFocus
Indicates that one entity is the primary subject, theme, or focal point of another entity’s creative work.
-
E.
researchContext
Indicates the situational, methodological, or thematic setting within which a particular piece of research is conducted or interpreted.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.