Triple
T8933554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liberian general election, 2005 |
E212717
|
entity |
| Predicate | votingSystemForLegislature |
P39112
|
FINISHED |
| Object | first-past-the-post |
—
|
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: first-past-the-post | Statement: [Liberian general election, 2005, votingSystemForLegislature, first-past-the-post]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemForLegislature Context triple: [Liberian general election, 2005, votingSystemForLegislature, first-past-the-post]
-
A.
electoralSystemForLegislature
chosen
Indicates the type of electoral system used to choose members of a particular legislature.
-
B.
votingSystemLokSabha
Indicates the type or method of voting system used for elections to the Lok Sabha.
-
C.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
D.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
E.
electionSystemFeature
Indicates that an election system possesses a specific characteristic, mechanism, or procedural feature related to how elections are conducted or managed.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc668fa87c8190bfeda820368b89e4 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.