Triple
T4596110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quicksort |
E100207
|
entity |
| Predicate | typicalPivotChoices |
P58205
|
FINISHED |
| Object | first element |
—
|
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: first element | Statement: [Quicksort, typicalPivotChoices, first element]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPivotChoices Context triple: [Quicksort, typicalPivotChoices, first element]
-
A.
typicalNumberOfSelections
Indicates the usual or expected count of selections made in a given choice or selection process.
-
B.
laterPivotedTo
Indicates that an entity changed direction, focus, or strategy at a subsequent time toward another specified activity, role, or domain.
-
C.
typicalPegRange
Indicates the usual or standard range of peg values within which something is normally maintained or expected to operate.
-
D.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
E.
typicalPickupConfiguration
Indicates the usual or standard arrangement or setup used for picking up or collecting something in a given context.
- 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_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. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.