Triple
T2576948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Convention (Germany) |
E56998
|
entity |
| Predicate | votingRounds |
P36526
|
FINISHED |
| Object | up to three ballots per election |
—
|
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: up to three ballots per election | Statement: [Federal Convention (Germany), votingRounds, up to three ballots per election]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingRounds Context triple: [Federal Convention (Germany), votingRounds, up to three ballots per election]
-
A.
votingOrder
Indicates the sequence or priority in which entities cast their votes or have their votes considered.
-
B.
numberOfBallots
chosen
Indicates the total count of ballots associated with a particular election, contest, or voting event.
-
C.
votingTiming
Indicates the temporal relationship specifying when a voting action occurs relative to a defined event or period.
-
D.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
E.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.