Triple
T1157358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Council of Provinces |
E24411
|
entity |
| Predicate | eachProvinceHasOneVote |
P3462
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [National Council of Provinces, eachProvinceHasOneVote, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eachProvinceHasOneVote Context triple: [National Council of Provinces, eachProvinceHasOneVote, true]
-
A.
votingUnit
chosen
Indicates a relationship where an entity functions as a unit or body that casts votes or participates in a voting process.
-
B.
numberOfProvinces
Indicates the total count of provinces associated with a given entity or within a specified region or country.
-
C.
seatOfElector
Indicates the location or jurisdiction that serves as the official base or constituency of a given elector.
-
D.
contestedInAllProvincesAndTerritories
Indicates that the event or process was actively challenged or opposed in every province and territory within the relevant jurisdiction.
-
E.
electorateState
Indicates the state or region in which a given electorate (voting district or constituency) is located or to which it belongs.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc92ae008190a587c12ecc9a502a |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.