Triple
T15256575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament of Botswana |
E364659
|
entity |
| Predicate | hasSpeciallyElectedMembersCount |
P117794
|
FINISHED |
| Object | 6 |
—
|
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: 6 | Statement: [Parliament of Botswana, hasSpeciallyElectedMembersCount, 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeciallyElectedMembersCount Context triple: [Parliament of Botswana, hasSpeciallyElectedMembersCount, 6]
-
A.
numberOfElectedMembers
Indicates the total count of individuals who have been formally chosen through an election to serve as members of a given body or group.
-
B.
hasElectedMembers
Indicates that an entity possesses members who have attained their positions through an election process.
-
C.
numberOfAppointedMembers
Indicates the specific count of members who have been formally appointed to a group, body, or position.
-
D.
numberOfDistrictMembers
Indicates the relationship that specifies how many members are associated with a given district.
-
E.
electoralRegionHasAdditionalMembers
Indicates that an electoral region is assigned additional representative members beyond its standard allocation.
- F. None of above. chosen
Provenance (4 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084b97908190b3bf7ea7bd75bdc0 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.