Triple
T34348177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish parliamentary election, 1997 |
E881493
|
entity |
| Predicate | totalSejmSeats |
P96187
|
FINISHED |
| Object | 460 |
—
|
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: 460 | Statement: [Polish parliamentary election, 1997, totalSejmSeats, 460]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalSejmSeats Context triple: [Polish parliamentary election, 1997, totalSejmSeats, 460]
-
A.
parliamentarySeatsTotal
chosen
Indicates the total number of seats in a given parliament or parliamentary body.
-
B.
seatsFreelyContestedInSejm
Indicates that the specified seats in the Sejm are filled through open, competitive elections without restrictions favoring particular parties or candidates.
-
C.
parliamentarySeats
Indicates the number of seats a party, group, or representative holds in a parliamentary body.
-
D.
oppositionVictoryInContestedSejmSeats
Indicates that the opposition won a majority of the contested seats in the Sejm.
-
E.
numberOfSeatsWon
Indicates the quantity of seats secured by an entity (such as a party or candidate) in an election or representative 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 1, 2026, 1:58 a.m.