Triple
T36972717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 Labour Party deputy leadership election |
E914611
|
entity |
| Predicate | successorDeputyLeader |
P33240
|
FINISHED |
| Object | Harriet Harman |
—
|
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: Harriet Harman | Statement: [2007 Labour Party deputy leadership election, successorDeputyLeader, Harriet Harman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDeputyLeader Context triple: [2007 Labour Party deputy leadership election, successorDeputyLeader, Harriet Harman]
-
A.
successorAsChief
Indicates that one entity becomes the next chief, taking over the leadership role from another entity.
-
B.
successorOfficeHolder
chosen
Indicates that one office holder directly follows another in occupying the same official position.
-
C.
laterAdministrativeSuccessor
Indicates that one administrative entity succeeds another in governing authority or jurisdiction at a later time.
-
D.
successorOfficeTo
Indicates that one office or position directly follows and replaces another in an official sequence or hierarchy.
-
E.
successorRole
Indicates that one role or position directly follows and replaces another in a sequence or organizational structure.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: May 3, 2026, 4:14 p.m.