Triple
T31814053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandy Silver |
E812085
|
entity |
| Predicate | officeAssumedAsPremierDate |
P88506
|
FINISHED |
| Object | 2016-12-03 |
—
|
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: 2016-12-03 | Statement: [Sandy Silver, officeAssumedAsPremierDate, 2016-12-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeAssumedAsPremierDate Context triple: [Sandy Silver, officeAssumedAsPremierDate, 2016-12-03]
-
A.
officeAssumedAt
chosen
Indicates the time or event at which an individual formally begins holding a particular office or position.
-
B.
officeAssumedAfter
Indicates that one entity began holding an office or position after another entity had already assumed that same office.
-
C.
officeEndAsPremier
Indicates the point in time or event at which an individual's term serving as premier comes to an end.
-
D.
assumedOfficeAsPremier
Indicates that an individual formally took up and began serving in the role of premier.
-
E.
officeAssumedAsPresidentFollowing
Indicates that one entity assumed the office of president immediately after another entity, in a direct succession.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: April 30, 2026, 11:44 p.m.