Triple

T28211369
Position Surface form Disambiguated ID Type / Status
Subject Condorcet criterion E711177 entity
Predicate satisfiedBy P4233 FINISHED
Object Schulze method
The Schulze method is a ranked-choice voting system that selects a winner by comparing the strength of paths between candidates in pairwise matchups, ensuring that any Condorcet winner is elected when one exists.
 E1816092 NE FINISHED

How this triple was built (3 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: Schulze method | Statement: [Condorcet criterion, satisfiedBy, Schulze method]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Schulze method
Triple: [Condorcet criterion, satisfiedBy, Schulze method]
Generated description
The Schulze method is a ranked-choice voting system that selects a winner by comparing the strength of paths between candidates in pairwise matchups, ensuring that any Condorcet winner is elected when one exists.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: satisfiedBy
Context triple: [Condorcet criterion, satisfiedBy, Schulze method]
  • A. satisfies chosen
    Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
  • B. saidToBeFulfilledBy
    Indicates that a requirement, condition, or expectation is claimed or considered to be satisfied by a particular entity or action.
  • C. satisfiedWithEqualityBy
    Indicates that one entity is content with or approves of another entity because they are treated or regarded as equal.
  • D. satisfiabilityType
    Indicates the classification of how or whether a given condition, formula, or constraint can be satisfied (e.g., satisfiable, unsatisfiable, or unknown).
  • E. determinedBy
    Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
  • F. None of above.

Provenance (6 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_69efb51cb5288190818c1f63a266af11 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69f64311726c81909e7b0211ec3f9058 completed May 2, 2026, 6:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a1632e95b6481909298211bc51a1ba9 completed May 26, 2026, 11:55 p.m.
NEDg Description generation batch_6a1634e773588190b0eda7b51b029b11 completed May 27, 2026, 12:03 a.m.
NED2 Entity disambiguation (via description) batch_6a1635789f2c8190ade17d4f34d65def completed May 27, 2026, 12:06 a.m.
PD Predicate disambiguation batch_69f641e0fde08190bf06a1c5b388aa84 completed May 2, 2026, 6:26 p.m.
Created at: April 27, 2026, 10:39 p.m.