Triple

T35237941
Position Surface form Disambiguated ID Type / Status
Subject South Dakota at-large congressional district E1017426 entity
Predicate isEqualToNumberOfSeatsForState P30282 FINISHED
Object 1 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: 1 | Statement: [South Dakota at-large congressional district, isEqualToNumberOfSeatsForState, 1]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isEqualToNumberOfSeatsForState
Context triple: [South Dakota at-large congressional district, isEqualToNumberOfSeatsForState, 1]
  • A. maximumSeatsPerState
    Indicates the upper limit on the number of seats that any single state is allowed to have.
  • B. minimumSeatsPerState
    Indicates the smallest number of seats that must be allocated to each state in a representative body or legislative apportionment.
  • C. hasSeatsForConstituency chosen
    Indicates that a governing body or institution allocates or provides a certain number of representative seats for a specific constituency.
  • D. numberOfSeatsInSenate
    Indicates the total count of seats allocated in a given senate.
  • E. hasNumberOfStatesAndDistricts
    Indicates a relationship where an entity is associated with a specific count of its constituent states and districts.
  • 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_69f76de235048190b990070c23c51b6b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78f63c8788190b253a18de5ca1312 completed May 3, 2026, 6:09 p.m.
PD Predicate disambiguation batch_69f78e2d71248190b850c2802ec170c0 completed May 3, 2026, 6:04 p.m.
Created at: May 3, 2026, 4:02 p.m.