Triple
T36972719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 Labour Party deputy leadership election |
E914611
|
entity |
| Predicate | ballotOf |
P186827
|
FINISHED |
| Object | Labour Party electoral college |
—
|
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: Labour Party electoral college | Statement: [2007 Labour Party deputy leadership election, ballotOf, Labour Party electoral college]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballotOf Context triple: [2007 Labour Party deputy leadership election, ballotOf, Labour Party electoral college]
-
A.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
B.
ballotNumber
Indicates the specific numerical identifier assigned to a ballot within an election or voting process.
-
C.
ballotStructure
Indicates how options, candidates, or choices are organized and presented on a ballot for selection.
-
D.
numberOfBallots
Indicates the total count of ballots associated with a particular election, contest, or voting event.
-
E.
ballotUnitUsed
Indicates that a particular ballot unit was utilized in the conduct of an election or voting process.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:14 p.m.