Triple

T31703767
Position Surface form Disambiguated ID Type / Status
Subject Arizona's congressional districts E809125 entity
Predicate previousApportionmentChange P156035 FINISHED
Object 2010 census 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: 2010 census | Statement: [Arizona's congressional districts, previousApportionmentChange, 2010 census]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: previousApportionmentChange
Context triple: [Arizona's congressional districts, previousApportionmentChange, 2010 census]
  • A. reapportionedAfter chosen
    Indicates that one entity’s allocation, distribution, or representation has been adjusted or reassigned as a consequence of another prior allocation event.
  • B. frequencyOfReapportionment
    Indicates how often reapportionment occurs within a given system or context.
  • C. apportionedAfter
    Indicates that one entity is distributed, allocated, or divided only after another specified event, action, or allocation has occurred.
  • D. apportionedBy
    Indicates that something is divided or allocated among parts or recipients according to a specified agent, rule, or method.
  • E. lastRedistrictingBasedOn
    Indicates the redistricting event or plan that most recently served as the basis for the current district boundaries.
  • 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_69f348de914081909fc8edff56f34dbe completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69fe7b1c506c8190869c1a22031e0571 completed May 9, 2026, 12:09 a.m.
PD Predicate disambiguation batch_69fe796b2bdc8190a86980d44008f875 completed May 9, 2026, 12:01 a.m.
Created at: April 30, 2026, 11:13 p.m.