Triple
T31784966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 United States Senate elections |
E811303
|
entity |
| Predicate | regularSeatsContested |
P11588
|
FINISHED |
| Object | 34 |
—
|
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: 34 | Statement: [2010 United States Senate elections, regularSeatsContested, 34]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularSeatsContested Context triple: [2010 United States Senate elections, regularSeatsContested, 34]
-
A.
numberOfSeatsContested
chosen
Indicates the total count of seats in an election or contest that are being competed for or are up for selection.
-
B.
numberOfSpecialSeatsContested
Indicates the total count of special or reserved seats that are being contested in an election or selection process.
-
C.
contestsSeatsIn
Indicates that an individual or party is competing for elected positions within a specified electoral district or governing body.
-
D.
portionOfSenateContested
Indicates the fraction of seats in a senate that are up for election or otherwise being contested during a given electoral cycle.
-
E.
areContestedIn
Indicates that something is the subject of dispute, challenge, or competition within a particular context, event, or process.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 30, 2026, 11:37 p.m.