Triple

T32896729
Position Surface form Disambiguated ID Type / Status
Subject Liberian general election, 2017 E841493 entity
Predicate wasRunoffRequired P139174 FINISHED
Object yes 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: yes | Statement: [Liberian general election, 2017, wasRunoffRequired, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasRunoffRequired
Context triple: [Liberian general election, 2017, wasRunoffRequired, yes]
  • A. presidentialRunoffRequired chosen
    Indicates that a second-round (runoff) presidential election must be held because no candidate met the required conditions for outright victory in the first round.
  • B. includeRunoffElections
    Indicates whether runoff elections are to be counted or considered as part of the election process or results.
  • C. runoffElectionDay
    Indicates the day on which a runoff election is held to determine a winner when no candidate achieved the required threshold in a prior election.
  • D. wasOnBallotIn
    Indicates that a candidate or option appeared as a choice on the official ballot in a specified election or voting event.
  • E. hasRunoffAreas
    Indicates that an entity includes or is equipped with designated runoff areas for managing excess water or liquid flow.
  • 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_69f34945ae408190b72d8118c83beb77 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d16f5cb881908eed141afaaa0b51 completed May 3, 2026, 4:39 a.m.
PD Predicate disambiguation batch_69f6cfe45554819089cbbd538d992132 completed May 3, 2026, 4:32 a.m.
Created at: May 1, 2026, 1:18 a.m.