Triple
T22325990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steven Sund |
E551902
|
entity |
| Predicate | inOfficeEndDate |
P140
|
FINISHED |
| Object | 2021-01-16 |
—
|
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: 2021-01-16 | Statement: [Steven Sund, inOfficeEndDate, 2021-01-16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inOfficeEndDate Context triple: [Steven Sund, inOfficeEndDate, 2021-01-16]
-
A.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
B.
endOfInstitutionDate
Indicates the date on which an institution’s existence, operation, or validity comes to an end.
-
C.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
D.
officeEnded
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
E.
previousOfficeEndTime
Indicates the time at which an entity’s immediately preceding office or position ended.
- 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15768696481909be124e86c23d551 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.