Triple

T11630692
Position Surface form Disambiguated ID Type / Status
Subject Bundestag electoral district E276387 entity
Predicate reasonForRedistricting P44846 FINISHED
Object population changes 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: population changes | Statement: [Bundestag electoral district, reasonForRedistricting, population changes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForRedistricting
Context triple: [Bundestag electoral district, reasonForRedistricting, population changes]
  • A. subjectToRedistricting
    Indicates that an entity’s boundaries, jurisdiction, or representation area can be changed through a formal redistricting process.
  • B. redistrictedBy
    Indicates that an entity’s boundaries or districts have been altered or redefined by another specified agent or authority.
  • C. notableRedistrictingEvent
    Indicates that a redistricting action or change to electoral boundaries is significant or noteworthy in its impact, controversy, or historical importance.
  • D. redistrictingBasis chosen
    Indicates the principle or criteria used as the foundation for drawing or adjusting electoral district boundaries.
  • E. redistrictedIn
    Indicates that the boundaries or jurisdiction of an area have been changed or reassigned within a specified district or administrative division.
  • 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_69d6aafa51148190ab84940694c00235 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a127b2688190ae3a340f851e834b completed April 10, 2026, 7:05 a.m.
PD Predicate disambiguation batch_69d85dd6503c819081f9045e9d5c4f3f completed April 10, 2026, 2:17 a.m.
Created at: April 8, 2026, 9:39 p.m.