Triple
T3216362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angus South |
E67403
|
entity |
| Predicate | electoralSystemFamily |
P539
|
FINISHED |
| Object | plurality voting |
—
|
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: plurality voting | Statement: [Angus South, electoralSystemFamily, plurality voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralSystemFamily Context triple: [Angus South, electoralSystemFamily, plurality voting]
-
A.
electoralSystemForLegislature
Indicates the type of electoral system used to choose members of a particular legislature.
-
B.
electoralSystemContext
Indicates the electoral system or framework within which a political or electoral event, action, or relationship takes place.
-
C.
electoralSystemConcerned
Indicates that something is related to, affected by, or focused on a particular electoral system.
-
D.
electionSystemFeature
Indicates that an election system possesses a specific characteristic, mechanism, or procedural feature related to how elections are conducted or managed.
-
E.
electionMethod
chosen
Indicates the process or system used to select a candidate or make a decision in an election.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab096b588190b22e41a76263ae92 |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.