Triple

T7756045
Position Surface form Disambiguated ID Type / Status
Subject New York City mayoral elections E175897 entity
Predicate termLimitsForElectedOffice P541 FINISHED
Object two consecutive terms 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: two consecutive terms | Statement: [New York City mayoral elections, termLimitsForElectedOffice, two consecutive terms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: termLimitsForElectedOffice
Context triple: [New York City mayoral elections, termLimitsForElectedOffice, two consecutive terms]
  • A. termLimitDefinedBy chosen
    Indicates that the duration or number of terms for holding a position is specified or constrained by a particular rule, law, or authority.
  • B. electsTermLength
    Indicates the length of time for which an entity is elected to hold a particular position or office.
  • C. termLength
    Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
  • D. termInOffice
    Indicates the period during which an individual officially holds a particular office or position.
  • E. officeHoldersNumberLimit
    Indicates a constraint specifying the maximum number of individuals who may simultaneously hold a particular office or position.
  • 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_69c6996180088190832e38e8d83ff54a completed March 27, 2026, 2:51 p.m.
NER Named-entity recognition batch_69c705257ca08190a78c592a1e616da8 completed March 27, 2026, 10:31 p.m.
PD Predicate disambiguation batch_69c7016df2b08190b2330a2010691431 completed March 27, 2026, 10:15 p.m.
Created at: March 27, 2026, 4:08 p.m.