Triple
T22809827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | October 1949 East German general election |
E564641
|
entity |
| Predicate | typeOfBallot |
P78405
|
FINISHED |
| Object | single list of candidates |
—
|
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: single list of candidates | Statement: [October 1949 East German general election, typeOfBallot, single list of candidates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBallot Context triple: [October 1949 East German general election, typeOfBallot, single list of candidates]
-
A.
hasBallotType
chosen
Indicates that an election, ballot, or voting process uses or is associated with a specific type or format of ballot.
-
B.
typeOfVoting
Indicates the specific method or system by which a vote is cast or recorded in a decision-making process.
-
C.
ballot
Indicates that an entity participates in a formal voting process, typically by casting or submitting a vote or choice.
-
D.
ballotStructure
Indicates how options, candidates, or choices are organized and presented on a ballot for selection.
-
E.
ballotUnitUsed
Indicates that a particular ballot unit was utilized in the conduct of an election or 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5f1f348190a35e87939732c99f |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.