Triple
T715427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrik Verwoerd |
E14302
|
entity |
| Predicate | officeEndAsPrimeMinister |
P371
|
FINISHED |
| Object | 1966-09-06 |
—
|
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: 1966-09-06 | Statement: [Hendrik Verwoerd, officeEndAsPrimeMinister, 1966-09-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeEndAsPrimeMinister Context triple: [Hendrik Verwoerd, officeEndAsPrimeMinister, 1966-09-06]
-
A.
primeMinisterTermEnd
chosen
Indicates the date or point in time when a person's tenure as prime minister comes to an end.
-
B.
succeededByPrimeMinister
Indicates that one prime minister directly follows another in office as their immediate successor.
-
C.
producedPrimeMinister
Indicates that one entity (typically a place, institution, or group) has been the origin or source of an individual who became a prime minister.
-
D.
primeMinisterFrom
Indicates that a person serves or has served as the prime minister of a specified country, region, or political entity.
-
E.
lastPrimeMinister
Indicates that the subject is the most recent individual to have held the office of prime minister of the object entity.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a574b4d881908b6d0be386081efd |
completed | March 1, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f38898819089d79bad4f4ff2d2 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.