Triple
T4689240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groysman Government |
E103993
|
entity |
| Predicate | voteForAppointment |
P5054
|
FINISHED |
| Object | 257 deputies |
—
|
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: 257 deputies | Statement: [Groysman Government, voteForAppointment, 257 deputies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteForAppointment Context triple: [Groysman Government, voteForAppointment, 257 deputies]
-
A.
voteFor
chosen
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
B.
voteRecord
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
-
C.
vote
Indicates that an entity formally expresses a choice or preference in a decision-making process, typically an election or poll.
-
D.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
E.
voteAgainst
Indicates that an entity formally expresses opposition to a proposal, decision, or candidate in a voting 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.