Triple
T20171826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Eshoo |
E491978
|
entity |
| Predicate | notableOfficeStartYear |
P138959
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Anna Eshoo, notableOfficeStartYear, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOfficeStartYear Context triple: [Anna Eshoo, notableOfficeStartYear, 1993]
-
A.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
-
B.
notableManagerTenureStart
Indicates the date or point in time when a manager’s particularly significant or distinguished period of managing an entity began.
-
C.
officeReestablishedYear
Indicates the year in which an office or official position was reestablished after having been previously discontinued or abolished.
-
D.
notableWorkPeriodStart
Indicates the point in time when an entity’s period of producing its notable work or works begins.
-
E.
notableProjectYear
Indicates the year in which a notable project associated with an entity took place, was created, or was prominently recognized.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e66848ae3c8190aa5fde66da35a89a |
completed | April 20, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:35 p.m.