Triple
T17647602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Eisenbud |
E429400
|
entity |
| Predicate | startTimeOfPositionAtMSRI |
P66434
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [David Eisenbud, startTimeOfPositionAtMSRI, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfPositionAtMSRI Context triple: [David Eisenbud, startTimeOfPositionAtMSRI, 1997]
-
A.
startTime_ma
Indicates the time at which an event, action, or relationship begins, measured in millions of years ago (Ma).
-
B.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
C.
positionStartTime
chosen
Indicates the time at which a position, role, or placement begins.
-
D.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
-
E.
startTimeAsConsort
Indicates the point in time when an individual began serving or being recognized as a consort in relation to another entity.
- 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_69d889e2c2608190b762e76d9b2262f1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46e3a5ad8819085d4bef669fc3152 |
completed | April 19, 2026, 5:55 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 6:05 a.m.