Triple
T1686630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neville Chamberlain |
E36455
|
entity |
| Predicate | resignedAsPrimeMinister |
P371
|
FINISHED |
| Object | 1940-05-10 |
—
|
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: 1940-05-10 | Statement: [Neville Chamberlain, resignedAsPrimeMinister, 1940-05-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resignedAsPrimeMinister Context triple: [Neville Chamberlain, resignedAsPrimeMinister, 1940-05-10]
-
A.
ledToPrimeMinisterResignation
Indicates that one event or action caused or significantly contributed to the resignation of a prime minister.
-
B.
succeededByPrimeMinister
Indicates that one prime minister directly follows another in office as their immediate successor.
-
C.
primeMinisterTermEnd
chosen
Indicates the date or point in time when a person's tenure as prime minister comes to an end.
-
D.
formerPrimeMinisterMP
Indicates that a person served as a prime minister in the past and also held a position as a member of parliament.
-
E.
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.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.