Triple
T36749609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suella Braverman |
E907867
|
entity |
| Predicate | appointedAsHomeSecretaryBy |
P257
|
FINISHED |
| Object | Liz Truss |
—
|
NE NERFINISHED |
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: Liz Truss | Statement: [Suella Braverman, appointedAsHomeSecretaryBy, Liz Truss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsHomeSecretaryBy Context triple: [Suella Braverman, appointedAsHomeSecretaryBy, Liz Truss]
-
A.
reappointedAsHomeSecretaryBy
Indicates that a person was again appointed to the position of Home Secretary by a specific appointing authority.
-
B.
precededByAsHomeSecretary
Indicates that one individual previously held the position of Home Secretary before another individual.
-
C.
appointedBy
chosen
Indicates that one entity has been formally selected or assigned to a position, role, or office by another entity.
-
D.
termStartAsHomeSecretary
Indicates the date or event when an individual officially begins their term serving in the role of Home Secretary.
-
E.
premierAppointedBy
Indicates that a premier is selected and officially given their position by a specified person, group, or authority.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:12 p.m.