Triple
T20071706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 United Kingdom general election |
E499753
|
entity |
| Predicate | seatsInHouseOfCommonsContested |
P69316
|
FINISHED |
| Object | 651 |
—
|
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: 651 | Statement: [1992 United Kingdom general election, seatsInHouseOfCommonsContested, 651]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatsInHouseOfCommonsContested Context triple: [1992 United Kingdom general election, seatsInHouseOfCommonsContested, 651]
-
A.
numberOfSeatsInHouseOfCommons
chosen
Indicates the total count of seats allocated in the House of Commons.
-
B.
numberOfSeatsContested
Indicates the total count of seats in an election or contest that are being competed for or are up for selection.
-
C.
numberOfSpecialSeatsContested
Indicates the total count of special or reserved seats that are being contested in an election or selection process.
-
D.
parliamentarySeats
Indicates the number of seats a party, group, or representative holds in a parliamentary body.
-
E.
contestsSeatsIn
Indicates that an individual or party is competing for elected positions within a specified electoral district or governing body.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66438633481908710907c48806499 |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:40 p.m.