Triple
T36651590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Tonkin |
E904868
|
entity |
| Predicate | termStartAsPremierOfWesternAustralia |
P186120
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [John Tonkin, termStartAsPremierOfWesternAustralia, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsPremierOfWesternAustralia Context triple: [John Tonkin, termStartAsPremierOfWesternAustralia, 1971]
-
A.
termStartAsGovernorOfTasmania
Indicates the date or time when an individual begins their tenure serving as Governor of Tasmania.
-
B.
firstPrimeMinisterTermStart
Indicates the date on which an entity began serving its first term as prime minister.
-
C.
termInOfficeAsPremierEnd
Indicates the date or point in time when an individual's term in office as premier comes to an end.
-
D.
termStartAsActingPrimeMinister
Indicates that a person’s term in office begins specifically in the capacity of acting prime minister, rather than as a fully appointed or elected prime minister.
-
E.
firstTermAsChiefMinisterStart
Indicates the date or time when an individual’s first term serving as Chief Minister began.
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.