Triple
T1157327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Council of Provinces |
E24411
|
entity |
| Predicate | hasSpecialDelegatesPerProvince |
P25404
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [National Council of Provinces, hasSpecialDelegatesPerProvince, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialDelegatesPerProvince Context triple: [National Council of Provinces, hasSpecialDelegatesPerProvince, 4]
-
A.
hasRegionalCommission
Indicates that an entity is associated with, overseen by, or falls under the jurisdiction of a specific regional commission.
-
B.
stateDelegation
Indicates that authority, responsibility, or decision-making power is transferred from a state-level entity to another entity to act on its behalf.
-
C.
hasNumberOfProvinces
Indicates the total count of provinces associated with a given entity.
-
D.
hasNumberOfConstituencies
Indicates the specific count of constituencies associated with an entity.
-
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. 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_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. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:44 p.m.