Triple

T251241
Position Surface form Disambiguated ID Type / Status
Subject Reedy Creek Improvement District E5150 entity
Predicate boardElectionMethod P2726 FINISHED
Object landowner voting 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: landowner voting | Statement: [Reedy Creek Improvement District, boardElectionMethod, landowner voting]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boardElectionMethod
Context triple: [Reedy Creek Improvement District, boardElectionMethod, landowner voting]
  • A. electionMethod
    Indicates the process or system used to select a candidate or make a decision in an election.
  • B. votingMethod chosen
    Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
  • C. membersAreElectedIn
    Indicates that the members of a group or body attain their positions through an election process held within a specified context or jurisdiction.
  • D. electedWith
    Indicates that one entity attained an elected position or office together with, or as part of the same electoral outcome as, another entity.
  • E. appliesToElectionType
    Indicates that a rule, condition, or attribute is relevant or applicable to a specific type or category of election.
  • 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_69a257c4bf688190a46ebbf411ab7473 completed Feb. 28, 2026, 2:49 a.m.
NER Named-entity recognition batch_69a25d38aba8819081d0958eb60ce27e completed Feb. 28, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69a25b665f8c8190aac6fcbba2a0eebb completed Feb. 28, 2026, 3:05 a.m.
Created at: Feb. 28, 2026, 2:54 a.m.