Triple

T34511020
Position Surface form Disambiguated ID Type / Status
Subject City of Houston municipal government E886019 entity
Predicate hasNumberOfAtLargeCouncilSeats P17214 FINISHED
Object 5 at-large positions 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: 5 at-large positions | Statement: [City of Houston municipal government, hasNumberOfAtLargeCouncilSeats, 5 at-large positions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNumberOfAtLargeCouncilSeats
Context triple: [City of Houston municipal government, hasNumberOfAtLargeCouncilSeats, 5 at-large positions]
  • A. numberOfAtLargeSeats chosen
    Indicates the total count of at-large seats (positions not tied to specific districts or subunits) associated with an entity.
  • B. hasNumberOfCouncillors
    Indicates the relationship that specifies how many councillors are associated with a given entity.
  • C. hasCouncilSeat
    Indicates that an entity holds a position or seat on a governing council.
  • D. hasPermanentSeats
    Indicates that certain entities hold ongoing, non-rotating positions or places within a defined structure or body.
  • E. hasMunicipalAssemblySeats
    Indicates the number of seats or positions a party, group, or entity holds in a municipal assembly or local council.
  • 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_69f349ccc290819089d8e82698e53cb6 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69feabcda59481908f2bc13b46fcced1 completed May 9, 2026, 3:36 a.m.
PD Predicate disambiguation batch_69feaabd63f88190b30dcf6dd2ea39d1 completed May 9, 2026, 3:32 a.m.
Created at: May 1, 2026, 2:01 a.m.