Triple
T11631223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German federal elections |
E276401
|
entity |
| Predicate | secondVoteFor |
P5054
|
FINISHED |
| Object | party list |
—
|
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: party list | Statement: [German federal elections, secondVoteFor, party list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondVoteFor Context triple: [German federal elections, secondVoteFor, party list]
-
A.
voteFor
chosen
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
B.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
C.
secondRoundCandidate
Indicates that an entity has advanced past an initial selection stage and is being considered as a candidate in a second round of evaluation or decision-making.
-
D.
voted
Indicates that an entity formally expressed a choice or decision, typically in an election, poll, or decision-making process, regarding another entity or option.
-
E.
secondLeader
Indicates that an entity serves as the second-ranking leader or deputy leader in relation to another entity.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25aa9188190ab13d79139f37e7e |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.