Triple

T4596131
Position Surface form Disambiguated ID Type / Status
Subject Quicksort E100207 entity
Predicate worstCaseOccursWhen P12708 FINISHED
Object array is already sorted with poor pivot choice 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: array is already sorted with poor pivot choice | Statement: [Quicksort, worstCaseOccursWhen, array is already sorted with poor pivot choice]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: worstCaseOccursWhen
Context triple: [Quicksort, worstCaseOccursWhen, array is already sorted with poor pivot choice]
  • A. occursWhen chosen
    Indicates that one event or condition happens at the same time or is triggered under the circumstances defined by another event or condition.
  • B. isMaximumWhen
    Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
  • C. worstAccidentInSystem
    Indicates that an accident is the most severe or damaging one within a given system or context.
  • D. isMinimumWhen
    Indicates that a value or state is at its smallest or least level precisely under certain specified conditions or circumstances.
  • E. occursAt
    Indicates that an event or action takes place at a specific time or location.
  • 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_69bd43cbc014819098b45f435908f88a completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd594055dc8190a50f1b4be2be1ba0 completed March 20, 2026, 2:27 p.m.
PD Predicate disambiguation batch_69bd522c811c81909aae4feadae33174 completed March 20, 2026, 1:57 p.m.
Created at: March 20, 2026, 1:11 p.m.