Triple
T1157325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Council of Provinces |
E24411
|
entity |
| Predicate | hasTotalDelegates |
P10538
|
FINISHED |
| Object | 90 |
—
|
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: 90 | Statement: [National Council of Provinces, hasTotalDelegates, 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalDelegates Context triple: [National Council of Provinces, hasTotalDelegates, 90]
-
A.
numberOfDelegates
chosen
Indicates the quantity of delegates associated with or assigned to a particular entity or event.
-
B.
nonVotingDelegatesCount
Indicates the number of delegates associated with an entity who do not possess voting rights in a given decision-making process.
-
C.
hasVotingMembers
Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
-
D.
hasElectedMembers
Indicates that an entity possesses members who have attained their positions through an election process.
-
E.
electsDelegatesTo
Indicates that one entity selects or votes to choose representatives (delegates) who will act or decide on its behalf in another body or process.
- 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.