Triple
T21009131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenian local elections |
E517497
|
entity |
| Predicate | votingSystemForMayors |
P97682
|
FINISHED |
| Object | two-round system |
—
|
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: two-round system | Statement: [Slovenian local elections, votingSystemForMayors, two-round system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemForMayors Context triple: [Slovenian local elections, votingSystemForMayors, two-round system]
-
A.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
B.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
C.
usesVotingSystemForHead
chosen
Indicates that a particular voting system is employed to select or appoint the head (leader) of an entity.
-
D.
mayorSelection
Indicates the process or outcome of choosing or appointing someone to serve as mayor of a place.
-
E.
electoralSystemPreference
Indicates a relationship where an entity expresses a favored or chosen type of electoral system over other possible systems.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3dcb5081909b06d6db10fefba6 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.