Triple
T2608537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | October 1974 United Kingdom general election |
E58718
|
entity |
| Predicate | seatsForElection |
P11588
|
FINISHED |
| Object | 635 |
—
|
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: 635 | Statement: [October 1974 United Kingdom general election, seatsForElection, 635]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatsForElection Context triple: [October 1974 United Kingdom general election, seatsForElection, 635]
-
A.
numberOfSeatsWon
Indicates the quantity of seats secured by an entity (such as a party or candidate) in an election or representative body.
-
B.
hasSeatsForConstituency
Indicates that a governing body or institution allocates or provides a certain number of representative seats for a specific constituency.
-
C.
legislativeAssemblySeats
Indicates the number of seats an entity holds or is allocated in a legislative assembly.
-
D.
votingSystemLokSabha
Indicates the type or method of voting system used for elections to the Lok Sabha.
-
E.
numberOfSeatsContested
chosen
Indicates the total count of seats in an election or contest that are being competed for or are up for selection.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:49 p.m.