Triple

T316999
Position Surface form Disambiguated ID Type / Status
Subject Massachusetts Senate E7728 entity
Predicate districtType P1680 FINISHED
Object single-member districts 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: single-member districts | Statement: [Massachusetts Senate, districtType, single-member districts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: districtType
Context triple: [Massachusetts Senate, districtType, single-member districts]
  • A. district
    Indicates that one entity is an administrative or electoral district that geographically contains or governs another entity.
  • B. regionType
    Indicates the classification or category of a region, specifying what kind of region it is (e.g., administrative, geographic, or functional).
  • C. urbanAreaType
    Indicates the classification of an area based on its urban characteristics or development type (e.g., city, town, suburb, metropolitan region).
  • D. electoralDistrictType chosen
    Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
  • E. municipality
    Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
  • 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_69a2e7e7af7881908890039d6be4e9b8 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ea65ca7081908093e6aaaf2d34f7 completed Feb. 28, 2026, 1:15 p.m.
PD Predicate disambiguation batch_69a2e943f12c8190883854aeed974260 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.