Triple
T32313849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randy Schekman |
E825574
|
entity |
| Predicate | startTimeAsEditorInChiefOf eLife |
P83463
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Randy Schekman, startTimeAsEditorInChiefOf eLife, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsEditorInChiefOf eLife Context triple: [Randy Schekman, startTimeAsEditorInChiefOf eLife, 2012]
-
A.
editorInChiefAtTimeOfPublication
Indicates that a person served as the editor-in-chief of a publication at the specific time that publication was released.
-
B.
formerEditorInChief
Indicates that a person previously held, but no longer holds, the position of editor-in-chief of a publication or organization.
-
C.
editorInChiefStart
chosen
Indicates the time or event at which an entity begins serving as editor-in-chief of a publication or organization.
-
D.
wasEditorOf
Indicates that one entity served in the role of editor for another entity, such as a publication, work, or collection.
-
E.
originalEditorInChief
Indicates the person who first held the role of editor-in-chief for a given publication or work.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: May 1, 2026, 12:46 a.m.