Triple
T9631395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier of Yukon |
E232810
|
entity |
| Predicate | predecessorOfficeHolderStartTime |
P79591
|
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: [Premier of Yukon, predecessorOfficeHolderStartTime, 2016-12-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorOfficeHolderStartTime Context triple: [Premier of Yukon, predecessorOfficeHolderStartTime, 2016-12-03]
-
A.
lastOfficeHolderStartDate
Indicates the date on which the most recent person to hold a particular office or position began their term.
-
B.
officeHolderStartTime
Indicates the date and time at which an individual begins holding a particular office or position.
-
C.
precededByOfficeHolderTermStart
chosen
Indicates that the start of one office holder’s term occurs after and is directly preceded by the start of another office holder’s term.
-
D.
timeInOfficeBeginsIn
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
E.
precededByOfficeHolderTermEnd
Indicates that one office holder’s term began immediately after the end of another office holder’s term for the same position.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2621408190bfe2ea5a05359ee0 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:11 p.m.