Triple
T7001047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish legislative election of 1989 |
E162336
|
entity |
| Predicate | seatsContested |
P11588
|
FINISHED |
| Object | Sejm 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: Sejm 460 | Statement: [Polish legislative election of 1989, seatsContested, Sejm 460]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatsContested Context triple: [Polish legislative election of 1989, seatsContested, Sejm 460]
-
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.
contestsSeatsIn
Indicates that an individual or party is competing for elected positions within a specified electoral district or governing body.
-
C.
numberOfSeatsWon
Indicates the quantity of seats secured by an entity (such as a party or candidate) in an election or representative body.
-
D.
electionContests
Indicates that one election is in competition with, or formally challenges the outcome or validity of, another election.
-
E.
parliamentarySeats
Indicates the number of seats a party, group, or representative holds in a parliamentary 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_69c68857ffc08190857dc62cd5253777 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc0f8830819091f4356296234713 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.