Triple
T28211366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Condorcet criterion |
E711177
|
entity |
| Predicate | notSatisfiedBy |
P164212
|
FINISHED |
| Object | Borda count |
—
|
NE NERFINISHED |
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: Borda count | Statement: [Condorcet criterion, notSatisfiedBy, Borda count]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notSatisfiedBy Context triple: [Condorcet criterion, notSatisfiedBy, Borda count]
-
A.
notSufficientFor
Indicates that the presence or occurrence of one condition does not by itself guarantee or bring about the other condition.
-
B.
notEnforcedBy
Indicates that a rule, policy, or obligation is not upheld, imposed, or carried out by the referenced enforcing entity.
-
C.
satisfies
Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
-
D.
nonEligibility
Indicates that an entity does not meet the required conditions or criteria to qualify for a specified status, benefit, or action.
-
E.
notEstablishedBy
Indicates that a given entity, state, or condition does not originate from, is not created by, and is not the result of the specified agent or source.
- F. None of above. chosen
Provenance (4 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_69f643c204508190a43fe0ec5165b01c |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 27, 2026, 10:39 p.m.