Triple
T18791218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insertion sort |
E459517
|
entity |
| Predicate | worstCaseInput |
P86607
|
FINISHED |
| Object | reverse sorted array |
—
|
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: reverse sorted array | Statement: [Insertion sort, worstCaseInput, reverse sorted array]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worstCaseInput Context triple: [Insertion sort, worstCaseInput, reverse sorted array]
-
A.
maximumNumber
Indicates that one entity specifies the highest allowable or observed quantity, value, or count associated with another entity.
-
B.
worstValueMeaning
chosen
Indicates that the associated value represents the least favorable or most undesirable outcome or condition within a given context or scale.
-
C.
maximumWeight
Indicates the greatest allowable or observed weight value associated with an entity or relationship.
-
D.
identifiesMaximumWith
Indicates that one entity designates or associates another entity as having the greatest value, degree, or extent within a specified set or context.
-
E.
loserElimination
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978665388190aaefed0ec30a1ff3 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.