Triple
T18791081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomuto partition scheme |
E459514
|
entity |
| Predicate | usesSwaps |
P109912
|
FINISHED |
| Object | to move elements less than pivot to left side |
—
|
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: to move elements less than pivot to left side | Statement: [Lomuto partition scheme, usesSwaps, to move elements less than pivot to left side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSwaps Context triple: [Lomuto partition scheme, usesSwaps, to move elements less than pivot to left side]
-
A.
hotSwappable
Indicates that one component can be removed and replaced with another while the overall system remains powered on and operational.
-
B.
usesMove
chosen
Indicates that an entity performs or executes a specific move or action.
-
C.
hasBodySwapWith
Indicates a reciprocal relationship where two entities have exchanged bodies or physical forms with each other.
-
D.
hasSiblingExchange
Indicates a reciprocal relationship in which two entities are siblings of each other.
-
E.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
- 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.