Triple
T7000941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solidarity Electoral Action |
E162334
|
entity |
| Predicate | electoralResult |
P40173
|
FINISHED |
| Object | 1997 Sejm – about 33.8% of the vote |
—
|
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: 1997 Sejm – about 33.8% of the vote | Statement: [Solidarity Electoral Action, electoralResult, 1997 Sejm – about 33.8% of the vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralResult Context triple: [Solidarity Electoral Action, electoralResult, 1997 Sejm – about 33.8% of the vote]
-
A.
electoralVoteOutcome
chosen
Indicates the result of an election in terms of how electoral votes are allocated or distributed among candidates or options.
-
B.
statusOfElections
Indicates the current condition or phase of one or more elections, such as whether they are upcoming, ongoing, or completed.
-
C.
politicalOutcome
Indicates the result or consequence of a political process, decision, event, or interaction.
-
D.
referendumResult
Indicates the outcome or decision reached by voters in a specific referendum.
-
E.
electoralSuccess
Indicates that an entity has achieved a favorable or winning outcome in an election or electoral 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_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.